Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6e57b5e66bdf1b0f15846a6bc2f6d945e5c4bd1fbdaa1dfc0d6526012f3f9dd

Tx prefix hash: b36950c1aa99579303e3c04c97cbc2d35b2899eef152a7b1ec5811ac7f3aeb73
Tx public key: 55cc9d2ce06a6e0875ae95f6578aabfe135e0ada899e49fead97594936a304a2
Timestamp: 1711247414 Timestamp [UCT]: 2024-03-24 02:30:14 Age [y:d:h:m:s]: 01:285:05:39:38
Block: 985013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462608 RingCT/type: yes/0
Extra: 0155cc9d2ce06a6e0875ae95f6578aabfe135e0ada899e49fead97594936a304a20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e8e80277578ff763363c04a98a952e2eb4075fa73f0ad1c2c492cd79ca30b8e 0.600000000000 1445218 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": 985023, "vin": [ { "gen": { "height": 985013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e8e80277578ff763363c04a98a952e2eb4075fa73f0ad1c2c492cd79ca30b8e" } } ], "extra": [ 1, 85, 204, 157, 44, 224, 106, 110, 8, 117, 174, 149, 246, 87, 138, 171, 254, 19, 94, 10, 218, 137, 158, 73, 254, 173, 151, 89, 73, 54, 163, 4, 162, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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