Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 290654a6357cb66ed8e769aa983070563538188bf893b8848fcd0554e3b23893

Tx prefix hash: c16a4c084acd178daa3225df7a94e343e05987d11985b54974d200066a280171
Tx public key: aac57c4f0d7192d962f23b266aeb7fd6dbe5b983bf74aea508ceb159081357c4
Timestamp: 1759881822 Timestamp [UCT]: 2025-10-08 00:03:42 Age [y:d:h:m:s]: 00:040:22:59:26
Block: 1385070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29334 RingCT/type: yes/0
Extra: 01aac57c4f0d7192d962f23b266aeb7fd6dbe5b983bf74aea508ceb159081357c402110000000297baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04fe5ed8c690503cd797c07ba42c4f107aa2ecbd3928584479327c1d2a94bfa1 0.600000000000 1873227 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": 1385080, "vin": [ { "gen": { "height": 1385070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04fe5ed8c690503cd797c07ba42c4f107aa2ecbd3928584479327c1d2a94bfa1" } } ], "extra": [ 1, 170, 197, 124, 79, 13, 113, 146, 217, 98, 242, 59, 38, 106, 235, 127, 214, 219, 229, 185, 131, 191, 116, 174, 165, 8, 206, 177, 89, 8, 19, 87, 196, 2, 17, 0, 0, 0, 2, 151, 186, 249, 34, 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