Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ddbb9b8f1c4cbe1a7a80ac165504877363135ed29f632f4aef35567d824eb16

Tx prefix hash: 4ef9ba1f772104e78516d3c544ded0d9ec0c6df3c3e521bac6298f2b07fba0aa
Tx public key: 166478404a38d9365622f60193d80f6dff2b8729ff9b5b6fda02e7ac9edd6f0e
Timestamp: 1745279328 Timestamp [UCT]: 2025-04-21 23:48:48 Age [y:d:h:m:s]: 00:020:22:52:13
Block: 1266618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14985 RingCT/type: yes/0
Extra: 01166478404a38d9365622f60193d80f6dff2b8729ff9b5b6fda02e7ac9edd6f0e021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10d26e71d21a66020a910e5bf118f7dc44c29fed7ec222cd2c3b0d830775bcf2 0.600000000000 1753839 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": 1266628, "vin": [ { "gen": { "height": 1266618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10d26e71d21a66020a910e5bf118f7dc44c29fed7ec222cd2c3b0d830775bcf2" } } ], "extra": [ 1, 22, 100, 120, 64, 74, 56, 217, 54, 86, 34, 246, 1, 147, 216, 15, 109, 255, 43, 135, 41, 255, 155, 91, 111, 218, 2, 231, 172, 158, 221, 111, 14, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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