Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60600e39391687cdbde47e1443d71603cb69a237f57832b4032a4db2297124bf

Tx prefix hash: 5f90dc8b2f8eedd2122e5e81e52d5e11d019980c1845e9b064cb78b35db4b846
Tx public key: aafc67366a626d6f1729d88e83e0911ff6b92317dbc9dda00792954a2b8d93b6
Timestamp: 1709135368 Timestamp [UCT]: 2024-02-28 15:49:28 Age [y:d:h:m:s]: 01:055:11:36:25
Block: 967491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300673 RingCT/type: yes/0
Extra: 01aafc67366a626d6f1729d88e83e0911ff6b92317dbc9dda00792954a2b8d93b60211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d908353914fbb4282249520fbe253e0991edb2ab88c338b411028cee8036238b 0.600000000000 1427272 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": 967501, "vin": [ { "gen": { "height": 967491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d908353914fbb4282249520fbe253e0991edb2ab88c338b411028cee8036238b" } } ], "extra": [ 1, 170, 252, 103, 54, 106, 98, 109, 111, 23, 41, 216, 142, 131, 224, 145, 31, 246, 185, 35, 23, 219, 201, 221, 160, 7, 146, 149, 74, 43, 141, 147, 182, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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