Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb0297b626c21edac9d09f58b813a55d80f538ed5c11b5977478031c818ded87

Tx prefix hash: db7178b7eb907d75a5e1dbee340f2e283c8948067c98961bbd5b10a85fd1f243
Tx public key: ffa6867ed4b9ab821bf6aff66137a29a2fb12e14e8f75d7ac9b3966a33a3a934
Timestamp: 1703162586 Timestamp [UCT]: 2023-12-21 12:43:06 Age [y:d:h:m:s]: 01:144:03:06:37
Block: 917960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364160 RingCT/type: yes/0
Extra: 01ffa6867ed4b9ab821bf6aff66137a29a2fb12e14e8f75d7ac9b3966a33a3a93402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1751d6f81f65cde370161df23fc8cad94eb83f716b25e0526932e50b721b81c 0.600000000000 1375590 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": 917970, "vin": [ { "gen": { "height": 917960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1751d6f81f65cde370161df23fc8cad94eb83f716b25e0526932e50b721b81c" } } ], "extra": [ 1, 255, 166, 134, 126, 212, 185, 171, 130, 27, 246, 175, 246, 97, 55, 162, 154, 47, 177, 46, 20, 232, 247, 93, 122, 201, 179, 150, 106, 51, 163, 169, 52, 2, 17, 0, 0, 0, 1, 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