Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 929b8efeaca0bebcd86f98126bdb48cb3f52a06add7457ca9635e1b9da0bef6a

Tx prefix hash: aaf4d8734919c5475c6d4e5335ca259f0bc93503079a4218d24ec8fcc724ecd0
Tx public key: d790e644c4b6feedb49299e9a8d0b49dde1d30f0ca4360e48083732db46b975c
Timestamp: 1702210801 Timestamp [UCT]: 2023-12-10 12:20:01 Age [y:d:h:m:s]: 01:187:18:49:00
Block: 910074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395294 RingCT/type: yes/0
Extra: 01d790e644c4b6feedb49299e9a8d0b49dde1d30f0ca4360e48083732db46b975c02110000000be6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c00e04efe1e6055d0a4c1de5ca0ded3043d1629f7f807e9ff79b740d3da81882 0.600000000000 1367217 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": 910084, "vin": [ { "gen": { "height": 910074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c00e04efe1e6055d0a4c1de5ca0ded3043d1629f7f807e9ff79b740d3da81882" } } ], "extra": [ 1, 215, 144, 230, 68, 196, 182, 254, 237, 180, 146, 153, 233, 168, 208, 180, 157, 222, 29, 48, 240, 202, 67, 96, 228, 128, 131, 115, 45, 180, 107, 151, 92, 2, 17, 0, 0, 0, 11, 230, 210, 127, 156, 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