Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c20b2ec03be9394d1c113c61691b5397e1b9c1c1fae9b3f03b278f022f9bbf21

Tx prefix hash: ebd97d7d05906709ce07d65c7fad624df897ac850d09edd1e813d1951e0ebfbf
Tx public key: 528d953ced4ca88421e1928016fe8b99a1a09532df234993acbfcc6ed4fc0e30
Timestamp: 1737483358 Timestamp [UCT]: 2025-01-21 18:15:58 Age [y:d:h:m:s]: 00:303:06:03:57
Block: 1202297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214278 RingCT/type: yes/0
Extra: 01528d953ced4ca88421e1928016fe8b99a1a09532df234993acbfcc6ed4fc0e30021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5850665f19264e8bf8c5f5d54da4a890899441df4fcca0aefd6a8567e9188d3a 0.600000000000 1688960 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": 1202307, "vin": [ { "gen": { "height": 1202297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5850665f19264e8bf8c5f5d54da4a890899441df4fcca0aefd6a8567e9188d3a" } } ], "extra": [ 1, 82, 141, 149, 60, 237, 76, 168, 132, 33, 225, 146, 128, 22, 254, 139, 153, 161, 160, 149, 50, 223, 35, 73, 147, 172, 191, 204, 110, 212, 252, 14, 48, 2, 17, 0, 0, 0, 3, 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