Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b71f971eac6cbcb16c50fe27f681f5ea8a865a38bd2277c1da3fc046c50d893

Tx prefix hash: 76daf369971ce92d429e153760ccd4589ad9333d0650221a0e925632b8e1f25b
Tx public key: ee3baddc8a0a84785b9b239abd2bf8fe80591b9f930a799e799485a64a793638
Timestamp: 1734768043 Timestamp [UCT]: 2024-12-21 08:00:43 Age [y:d:h:m:s]: 00:018:18:44:38
Block: 1179898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13410 RingCT/type: yes/0
Extra: 01ee3baddc8a0a84785b9b239abd2bf8fe80591b9f930a799e799485a64a793638021100000019007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 804ad9e6bfae781ea1681ea278913179c801c34212e2dae6cc1a6e23bf7123d3 0.600000000000 1666299 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": 1179908, "vin": [ { "gen": { "height": 1179898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "804ad9e6bfae781ea1681ea278913179c801c34212e2dae6cc1a6e23bf7123d3" } } ], "extra": [ 1, 238, 59, 173, 220, 138, 10, 132, 120, 91, 155, 35, 154, 189, 43, 248, 254, 128, 89, 27, 159, 147, 10, 121, 158, 121, 148, 133, 166, 74, 121, 54, 56, 2, 17, 0, 0, 0, 25, 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