Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 976f5c997e4a33be1632fcb0e8efc12d3f0585e9f03aa3bef240f59a52cae4ff

Tx prefix hash: 35f43eac558644ed3d7fb3d62b3f2f2a4f2d4f79696362457ced9109e37914ec
Tx public key: 9a907077ae59ea164d9a2ed8498cc77f4422266fb7d0a58b6d8b96a7c67dec58
Timestamp: 1702716140 Timestamp [UCT]: 2023-12-16 08:42:20 Age [y:d:h:m:s]: 01:132:03:09:46
Block: 914265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355585 RingCT/type: yes/0
Extra: 019a907077ae59ea164d9a2ed8498cc77f4422266fb7d0a58b6d8b96a7c67dec5802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10dd89343fec9d2df0dc5a3f3ffbcd84c8b35be65b37e92715119ed75096dceb 0.600000000000 1371559 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": 914275, "vin": [ { "gen": { "height": 914265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10dd89343fec9d2df0dc5a3f3ffbcd84c8b35be65b37e92715119ed75096dceb" } } ], "extra": [ 1, 154, 144, 112, 119, 174, 89, 234, 22, 77, 154, 46, 216, 73, 140, 199, 127, 68, 34, 38, 111, 183, 208, 165, 139, 109, 139, 150, 167, 198, 125, 236, 88, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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