Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 511a18632e09ba5516d2cd32238c3ec42b20308ac1b96088df3f70e20d705904

Tx prefix hash: b9fe46f03471305b3213123a277d555cbe3e60336a6b61245462c0424b9738ec
Tx public key: 1d6b3e7cbd66c5fb1d0cef78c13f5defefbbb8173d01a183a7365c7888514d14
Timestamp: 1660609800 Timestamp [UCT]: 2022-08-16 00:30:00 Age [y:d:h:m:s]: 03:085:12:26:58
Block: 566736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 840926 RingCT/type: yes/0
Extra: 011d6b3e7cbd66c5fb1d0cef78c13f5defefbbb8173d01a183a7365c7888514d14021100000002ec6d1a1a000000000000000000

1 output(s) for total of 8.131458998000 dcy

stealth address amount amount idx
00: f3f7ea3416033d4d8b8f74dbb3a059d3e6cb5bee1979e86777f416261aa0ae6b 8.131458998000 999769 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": 566746, "vin": [ { "gen": { "height": 566736 } } ], "vout": [ { "amount": 8131458998, "target": { "key": "f3f7ea3416033d4d8b8f74dbb3a059d3e6cb5bee1979e86777f416261aa0ae6b" } } ], "extra": [ 1, 29, 107, 62, 124, 189, 102, 197, 251, 29, 12, 239, 120, 193, 63, 93, 239, 239, 187, 184, 23, 61, 1, 161, 131, 167, 54, 92, 120, 136, 81, 77, 20, 2, 17, 0, 0, 0, 2, 236, 109, 26, 26, 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