Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae1d200cd8d95b4b184e8047c93ba5c6c45b37d72f608f902407bb3f743317c6

Tx prefix hash: 8921ec0e5556800b47fb092e71e7e6c43446d3d9f386cff6c988800ba5328784
Tx public key: 373dd4307e6a1e8138cad987b20fb19275e317c69db4197dec2ce9e507927c4f
Timestamp: 1708992246 Timestamp [UCT]: 2024-02-27 00:04:06 Age [y:d:h:m:s]: 01:037:10:15:24
Block: 966304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287762 RingCT/type: yes/0
Extra: 01373dd4307e6a1e8138cad987b20fb19275e317c69db4197dec2ce9e507927c4f02110000001152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06aeb96242f4e6e5bd03b86b3393e34abfbb83b4d0d5e557042ce6788314b45f 0.600000000000 1426061 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": 966314, "vin": [ { "gen": { "height": 966304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06aeb96242f4e6e5bd03b86b3393e34abfbb83b4d0d5e557042ce6788314b45f" } } ], "extra": [ 1, 55, 61, 212, 48, 126, 106, 30, 129, 56, 202, 217, 135, 178, 15, 177, 146, 117, 227, 23, 198, 157, 180, 25, 125, 236, 44, 233, 229, 7, 146, 124, 79, 2, 17, 0, 0, 0, 17, 82, 212, 126, 148, 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