Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222ab2c382e88c0765527bd8f41c01602f1f74b6bf9bccc3075d60c6430fa79a

Tx prefix hash: e493ad15854e1e627369b8ffa1db70e54cd8d0eb848665de827bc1caa7b07f99
Tx public key: 15475f3e6e67e10c9aca9fb5dacf2e64bb7d8779eaa011029b6438d3eaadc88a
Timestamp: 1759960926 Timestamp [UCT]: 2025-10-08 22:02:06 Age [y:d:h:m:s]: 00:036:22:38:17
Block: 1385724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26469 RingCT/type: yes/0
Extra: 0115475f3e6e67e10c9aca9fb5dacf2e64bb7d8779eaa011029b6438d3eaadc88a02110000000797baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5e3c2931537d7f5e81400722388276ed63c81470ad0f21ffb01d53d8a7d2d8d 0.600000000000 1873887 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": 1385734, "vin": [ { "gen": { "height": 1385724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5e3c2931537d7f5e81400722388276ed63c81470ad0f21ffb01d53d8a7d2d8d" } } ], "extra": [ 1, 21, 71, 95, 62, 110, 103, 225, 12, 154, 202, 159, 181, 218, 207, 46, 100, 187, 125, 135, 121, 234, 160, 17, 2, 155, 100, 56, 211, 234, 173, 200, 138, 2, 17, 0, 0, 0, 7, 151, 186, 249, 34, 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