Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a06360d38f53f56a05298dc5f16549ef2a90b80543b2305f2e25d65cb0927373

Tx prefix hash: 16abe7edb1efc969c99e6d62af40a00467a8d55b51d75eae72eff51ca7651def
Tx public key: ab4f3a5bb409158d9b57c2460aa4483c80d46f9fda0022722c065dc73a2bb2cc
Timestamp: 1751028170 Timestamp [UCT]: 2025-06-27 12:42:50 Age [y:d:h:m:s]: 00:100:12:34:28
Block: 1313846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69829 RingCT/type: yes/0
Extra: 01ab4f3a5bb409158d9b57c2460aa4483c80d46f9fda0022722c065dc73a2bb2cc02110000000743846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52e57914301ba1424db834d82033ce90e4a8ff795e531fd1a98dc8e6affbaf5e 0.600000000000 1801489 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": 1313856, "vin": [ { "gen": { "height": 1313846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52e57914301ba1424db834d82033ce90e4a8ff795e531fd1a98dc8e6affbaf5e" } } ], "extra": [ 1, 171, 79, 58, 91, 180, 9, 21, 141, 155, 87, 194, 70, 10, 164, 72, 60, 128, 212, 111, 159, 218, 0, 34, 114, 44, 6, 93, 199, 58, 43, 178, 204, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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