Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f1454631006b83a236e8e6e01893b966db3a28f96e1b1b256eca7da81b6165c

Tx prefix hash: 7f852438541f4672cde7f767bf705119a752ce7045571b90423e7b3ad184ee19
Tx public key: 3042de4e5dc3d78a075ac97a85a03ff531d13a7f719b5186fdcae9e458167f89
Timestamp: 1720015011 Timestamp [UCT]: 2024-07-03 13:56:51 Age [y:d:h:m:s]: 00:287:18:19:59
Block: 1057682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205609 RingCT/type: yes/0
Extra: 013042de4e5dc3d78a075ac97a85a03ff531d13a7f719b5186fdcae9e458167f8902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62a982a971ff447db880705dd39f82f89ed26fbc1da21e81d92afd8b211b1b81 0.600000000000 1528121 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": 1057692, "vin": [ { "gen": { "height": 1057682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62a982a971ff447db880705dd39f82f89ed26fbc1da21e81d92afd8b211b1b81" } } ], "extra": [ 1, 48, 66, 222, 78, 93, 195, 215, 138, 7, 90, 201, 122, 133, 160, 63, 245, 49, 209, 58, 127, 113, 155, 81, 134, 253, 202, 233, 228, 88, 22, 127, 137, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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