Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b987f0f42617fc703717f1468550f78a67121d8b09c1813520406675b7d42e31

Tx prefix hash: ebedf8346b73b1031dd196eefcbb09cf612bd24d70c9f849985b000a10121a7a
Tx public key: 74a0de0d5ffff79b4fb9b020716eeaf903c10f88bce5140abb13eb8fb713be3b
Timestamp: 1638980069 Timestamp [UCT]: 2021-12-08 16:14:29 Age [y:d:h:m:s]: 02:354:02:09:28
Block: 391176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 771119 RingCT/type: yes/0
Extra: 0174a0de0d5ffff79b4fb9b020716eeaf903c10f88bce5140abb13eb8fb713be3b021100000001f6cc1430000000000000000000

1 output(s) for total of 31.036439377000 dcy

stealth address amount amount idx
00: 86d77f5ccfa4f90b4efc08a613dd58e0cf0929af3bf3aa36bef638041e67b923 31.036439377000 787419 of 0

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": 391186, "vin": [ { "gen": { "height": 391176 } } ], "vout": [ { "amount": 31036439377, "target": { "key": "86d77f5ccfa4f90b4efc08a613dd58e0cf0929af3bf3aa36bef638041e67b923" } } ], "extra": [ 1, 116, 160, 222, 13, 95, 255, 247, 155, 79, 185, 176, 32, 113, 110, 234, 249, 3, 193, 15, 136, 188, 229, 20, 10, 187, 19, 235, 143, 183, 19, 190, 59, 2, 17, 0, 0, 0, 1, 246, 204, 20, 48, 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