Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6072df28b5d5fdfed4e06025df0df4f839135b399960850fe197ec747466b496

Tx prefix hash: 78cfc6f680fcbe0f9525ff5ff4b1a4f00644f87018861b23b9f55b4835773b3a
Tx public key: fbcb1c471c5bc0d627c45c5428615c25823741dbf499404ad8df7c2e21c01778
Timestamp: 1752784316 Timestamp [UCT]: 2025-07-17 20:31:56 Age [y:d:h:m:s]: 00:170:07:10:13
Block: 1327648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120561 RingCT/type: yes/0
Extra: 01fbcb1c471c5bc0d627c45c5428615c25823741dbf499404ad8df7c2e21c01778021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ab36be1b10e2601d2f2259b7b692e540b1f677556330393a52faa61c9c3f8dc 0.600000000000 1815405 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": 1327658, "vin": [ { "gen": { "height": 1327648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ab36be1b10e2601d2f2259b7b692e540b1f677556330393a52faa61c9c3f8dc" } } ], "extra": [ 1, 251, 203, 28, 71, 28, 91, 192, 214, 39, 196, 92, 84, 40, 97, 92, 37, 130, 55, 65, 219, 244, 153, 64, 74, 216, 223, 124, 46, 33, 192, 23, 120, 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