Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d510f93e686719a722e3f32da47468e38f33f4066f41fbcc9512e72921efe4d0

Tx prefix hash: eeb10c0149f90967d88f8cffe94ad32aa97741da7cee13cd0faec42494544ab1
Tx public key: b9a23e248c56c72290832f0541d8ac6bc723e6643d3d9191a63204c6ae6e9784
Timestamp: 1763077070 Timestamp [UCT]: 2025-11-13 23:37:50 Age [y:d:h:m:s]: 00:039:15:19:16
Block: 1411559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28372 RingCT/type: yes/0
Extra: 01b9a23e248c56c72290832f0541d8ac6bc723e6643d3d9191a63204c6ae6e9784021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc67fd9408c564a5e4087b420b553a88f4707c4c4091778e0e2ca0d3d06a2c08 0.600000000000 1900022 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": 1411569, "vin": [ { "gen": { "height": 1411559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc67fd9408c564a5e4087b420b553a88f4707c4c4091778e0e2ca0d3d06a2c08" } } ], "extra": [ 1, 185, 162, 62, 36, 140, 86, 199, 34, 144, 131, 47, 5, 65, 216, 172, 107, 199, 35, 230, 100, 61, 61, 145, 145, 166, 50, 4, 198, 174, 110, 151, 132, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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