Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2919d43d0345ec0a5efe83bcc2a6e1f29e3185c708c1b4c59ccc5ed310baba0

Tx prefix hash: f9e5ab08b4d8445ff7e90ada6dbd9e3f2fa3e076b288514430807cfaa2be8630
Tx public key: 92a3d50d85a45abcc6b1c34ff80b4fb2632395380e431f47954c7c624632a3e5
Timestamp: 1743278390 Timestamp [UCT]: 2025-03-29 19:59:50 Age [y:d:h:m:s]: 00:279:20:09:28
Block: 1250059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197799 RingCT/type: yes/0
Extra: 0192a3d50d85a45abcc6b1c34ff80b4fb2632395380e431f47954c7c624632a3e50211000000049ba629df000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06a72e9a4378dd03c594057eb17212d414768bdb2e026b0160e2653f5a6d28e9 0.600000000000 1737106 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": 1250069, "vin": [ { "gen": { "height": 1250059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06a72e9a4378dd03c594057eb17212d414768bdb2e026b0160e2653f5a6d28e9" } } ], "extra": [ 1, 146, 163, 213, 13, 133, 164, 90, 188, 198, 177, 195, 79, 248, 11, 79, 178, 99, 35, 149, 56, 14, 67, 31, 71, 149, 76, 124, 98, 70, 50, 163, 229, 2, 17, 0, 0, 0, 4, 155, 166, 41, 223, 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