Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85495a3355eabea971af58085f528bb596369f6ad3e9653a6b2a6c302ccf47d6

Tx prefix hash: 5462713604c248db98cadaf694c1ddd4a9369eea5e020d38c0f9476a63910518
Tx public key: d6473745234e5105222db1e8a9032b5d541297ba3e1323d9d6d0e75fce651234
Timestamp: 1715430079 Timestamp [UCT]: 2024-05-11 12:21:19 Age [y:d:h:m:s]: 01:017:18:41:24
Block: 1019697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273630 RingCT/type: yes/0
Extra: 01d6473745234e5105222db1e8a9032b5d541297ba3e1323d9d6d0e75fce65123402110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21e692c7fd3d5dabad671f2ed6a7eb2fef713a3da8bf524d14837d9b7761a3f9 0.600000000000 1483738 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": 1019707, "vin": [ { "gen": { "height": 1019697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21e692c7fd3d5dabad671f2ed6a7eb2fef713a3da8bf524d14837d9b7761a3f9" } } ], "extra": [ 1, 214, 71, 55, 69, 35, 78, 81, 5, 34, 45, 177, 232, 169, 3, 43, 93, 84, 18, 151, 186, 62, 19, 35, 217, 214, 208, 231, 95, 206, 101, 18, 52, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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