Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72521b33124813160cbc2de312ef6c372b23bd8050f234d9b91278bc934c02f8

Tx prefix hash: 7a675aef7fc00c8fa133a5c1763fa4c162069ef7f8b713c169616e2b72c73ed7
Tx public key: 99ed6ef6b360c3d4eb2be13a7dfa087d202023f73f8820ee96e368cfe8511e02
Timestamp: 1729477007 Timestamp [UCT]: 2024-10-21 02:16:47 Age [y:d:h:m:s]: 00:208:18:54:03
Block: 1136084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149050 RingCT/type: yes/0
Extra: 0199ed6ef6b360c3d4eb2be13a7dfa087d202023f73f8820ee96e368cfe8511e02021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0e9bff6be3561c197edeb6592a0d7375d9ee0b795c61fdee26e3c51e69267d5 0.600000000000 1619427 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": 1136094, "vin": [ { "gen": { "height": 1136084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0e9bff6be3561c197edeb6592a0d7375d9ee0b795c61fdee26e3c51e69267d5" } } ], "extra": [ 1, 153, 237, 110, 246, 179, 96, 195, 212, 235, 43, 225, 58, 125, 250, 8, 125, 32, 32, 35, 247, 63, 136, 32, 238, 150, 227, 104, 207, 232, 81, 30, 2, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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