Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbbabd1c036e91be34d25ea0209a870f36be2fb704682561099482bb6f8a1d2a

Tx prefix hash: 35a7272642ddcc593931a6c0af0f2c54816804d5922e1fbadd66d6c19a924c41
Tx public key: e8f46897f89b60b3958f9ddbdf6cb4fd5e009870e7a2e786667719a37d9e47ac
Timestamp: 1733180207 Timestamp [UCT]: 2024-12-02 22:56:47 Age [y:d:h:m:s]: 00:161:02:34:45
Block: 1166730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114964 RingCT/type: yes/0
Extra: 01e8f46897f89b60b3958f9ddbdf6cb4fd5e009870e7a2e786667719a37d9e47ac021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c9e37117fde3030ebac81881300ce68019bd24261581255ff6692e57f4b62a3 0.600000000000 1652419 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": 1166740, "vin": [ { "gen": { "height": 1166730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c9e37117fde3030ebac81881300ce68019bd24261581255ff6692e57f4b62a3" } } ], "extra": [ 1, 232, 244, 104, 151, 248, 155, 96, 179, 149, 143, 157, 219, 223, 108, 180, 253, 94, 0, 152, 112, 231, 162, 231, 134, 102, 119, 25, 163, 125, 158, 71, 172, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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