Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d34bd782403e2ba8261da7440b9ea5b98cad5649dd19c8ee7c8689a39cc2d01

Tx prefix hash: 51e21be9658fd4e39d123c64097c6bdc655bc49ca179c21b0afa354e965e2bfb
Tx public key: 90996f109b40666bfc096182be1e9dcf44b2d3956d8b2e3bed6f9e2f63fb3196
Timestamp: 1761709427 Timestamp [UCT]: 2025-10-29 03:43:47 Age [y:d:h:m:s]: 00:074:02:47:24
Block: 1400239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53059 RingCT/type: yes/0
Extra: 0190996f109b40666bfc096182be1e9dcf44b2d3956d8b2e3bed6f9e2f63fb3196021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a545d065c8fbcba802ece26bb74e275fdfb0e0633b5d3b8dbd8e26cb1451060 0.600000000000 1888546 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": 1400249, "vin": [ { "gen": { "height": 1400239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a545d065c8fbcba802ece26bb74e275fdfb0e0633b5d3b8dbd8e26cb1451060" } } ], "extra": [ 1, 144, 153, 111, 16, 155, 64, 102, 107, 252, 9, 97, 130, 190, 30, 157, 207, 68, 178, 211, 149, 109, 139, 46, 59, 237, 111, 158, 47, 99, 251, 49, 150, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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