Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec15379fa53827c0f5560832e5815be858599d4a82ea66ae46ad125ea8cf807a

Tx prefix hash: 02222fd07042a6dc78e23a9d0fcb7e3f1b4f6b0ead6405c4fd093fed2f031b05
Tx public key: b33bf59457bd2119e653598a0d60ddc70725729c301fd1cb3c36d4d81408b3f0
Timestamp: 1711368178 Timestamp [UCT]: 2024-03-25 12:02:58 Age [y:d:h:m:s]: 01:016:12:15:56
Block: 986020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272746 RingCT/type: yes/0
Extra: 01b33bf59457bd2119e653598a0d60ddc70725729c301fd1cb3c36d4d81408b3f00211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ad3187646de3122041086145a4c62f9e7194017bfe6ab9c653dcbc2518c7498 0.600000000000 1446245 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": 986030, "vin": [ { "gen": { "height": 986020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ad3187646de3122041086145a4c62f9e7194017bfe6ab9c653dcbc2518c7498" } } ], "extra": [ 1, 179, 59, 245, 148, 87, 189, 33, 25, 230, 83, 89, 138, 13, 96, 221, 199, 7, 37, 114, 156, 48, 31, 209, 203, 60, 54, 212, 216, 20, 8, 179, 240, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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