Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2e77195a9195db34d5dc373ffd024cb71164ab384442c4593e0b531cf4c3978e

Tx prefix hash: 03b71956ede12a96bdf429b871e07fa3e27b2e3c48629b126f13f147960be31d
Tx public key: af1e23f90f88abb9b3c70b518a6d8ed99e599d14a2a05db7a2304cf7cca5acbe
Timestamp: 1722613678 Timestamp [UCT]: 2024-08-02 15:47:58 Age [y:d:h:m:s]: 00:253:19:43:20
Block: 1079231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181302 RingCT/type: yes/0
Extra: 01af1e23f90f88abb9b3c70b518a6d8ed99e599d14a2a05db7a2304cf7cca5acbe02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c1e9f3381c659412492179edb83749569fdd77d8d9b55d1f3138e48afbe30d 0.600000000000 1552090 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1079241, "vin": [ { "gen": { "height": 1079231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c1e9f3381c659412492179edb83749569fdd77d8d9b55d1f3138e48afbe30d" } } ], "extra": [ 1, 175, 30, 35, 249, 15, 136, 171, 185, 179, 199, 11, 81, 138, 109, 142, 217, 158, 89, 157, 20, 162, 160, 93, 183, 162, 48, 76, 247, 204, 165, 172, 190, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8