Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93bc6e6ee5844809bd83632ab539b4ae8c2ddcdf9a75ce9984697366fecf514c

Tx prefix hash: 3ec26775c2286f832ecb7824073293f9c5341b8efc1c2182b01467afc7efd2ca
Tx public key: eb8ebc93b3910e1c52455f2dff0d0ab286dd22db08bbe3fd4b1d064fd61583a0
Timestamp: 1741409788 Timestamp [UCT]: 2025-03-08 04:56:28 Age [y:d:h:m:s]: 00:257:20:43:09
Block: 1234595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182023 RingCT/type: yes/0
Extra: 01eb8ebc93b3910e1c52455f2dff0d0ab286dd22db08bbe3fd4b1d064fd61583a00211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b34ac99372d1761375f647f4446765dcff0be7bfda92d67f6ddff76c782642c9 0.600000000000 1721526 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": 1234605, "vin": [ { "gen": { "height": 1234595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b34ac99372d1761375f647f4446765dcff0be7bfda92d67f6ddff76c782642c9" } } ], "extra": [ 1, 235, 142, 188, 147, 179, 145, 14, 28, 82, 69, 95, 45, 255, 13, 10, 178, 134, 221, 34, 219, 8, 187, 227, 253, 75, 29, 6, 79, 214, 21, 131, 160, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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