Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b34423bb86269ad7b1238d4da3203a936a35e1c2917ad56b3893dcc28807891c

Tx prefix hash: 286a061968a02558b70df8a55e1a82dd17fbd895a9d3be823b756084bc511623
Tx public key: 651e73fb3f30fdc2cb67fc3d2102ef1a57139d50e8eed79f1cbef4b477c6c14b
Timestamp: 1757364530 Timestamp [UCT]: 2025-09-08 20:48:50 Age [y:d:h:m:s]: 00:106:03:28:31
Block: 1364307 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75908 RingCT/type: yes/0
Extra: 01651e73fb3f30fdc2cb67fc3d2102ef1a57139d50e8eed79f1cbef4b477c6c14b021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63d031b6d6a0219187367acf44112ebe2710077344f48017c7fb43c66bf14f34 0.600000000000 1852346 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": 1364317, "vin": [ { "gen": { "height": 1364307 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63d031b6d6a0219187367acf44112ebe2710077344f48017c7fb43c66bf14f34" } } ], "extra": [ 1, 101, 30, 115, 251, 63, 48, 253, 194, 203, 103, 252, 61, 33, 2, 239, 26, 87, 19, 157, 80, 232, 238, 215, 159, 28, 190, 244, 180, 119, 198, 193, 75, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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