Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 581c5b61535eac8a6f26d6c6d0116e9bd636be6247198ada430accc838d2b95b

Tx prefix hash: 1862cd3e580db11e49616df293ea7658d3108345bb8f7db13f91be4abca9f404
Tx public key: 5acf8ea5f50242ff56eaa23360603074b5de81d136fa62d6b6c4cf95652ae3a6
Timestamp: 1762478356 Timestamp [UCT]: 2025-11-07 01:19:16 Age [y:d:h:m:s]: 00:060:20:26:40
Block: 1406589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43582 RingCT/type: yes/0
Extra: 015acf8ea5f50242ff56eaa23360603074b5de81d136fa62d6b6c4cf95652ae3a6021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ff99fd57e42a3f0720a304dc43991926a88b556556f85ec3af631d7514aacd 0.600000000000 1894976 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": 1406599, "vin": [ { "gen": { "height": 1406589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ff99fd57e42a3f0720a304dc43991926a88b556556f85ec3af631d7514aacd" } } ], "extra": [ 1, 90, 207, 142, 165, 245, 2, 66, 255, 86, 234, 162, 51, 96, 96, 48, 116, 181, 222, 129, 209, 54, 250, 98, 214, 182, 196, 207, 149, 101, 42, 227, 166, 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