Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 171aa096a23739349c62f722fe761aba3378f0e0266f82a2342e287fec25dd0b

Tx prefix hash: 1d1c9030afa3a6d14578cd90776afe9ad38187b47f09251143a04b9b6110da2f
Tx public key: 54931cf6ee14603cc04dcfa846b0c23ae6f04c8dd46a865b2b4ca01da52763f9
Timestamp: 1712078102 Timestamp [UCT]: 2024-04-02 17:15:02 Age [y:d:h:m:s]: 01:211:12:12:44
Block: 991847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409879 RingCT/type: yes/0
Extra: 0154931cf6ee14603cc04dcfa846b0c23ae6f04c8dd46a865b2b4ca01da52763f90211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aeb9a4e7cc7bc3e6785a2c301788d953a3832a77330a75a2745cf9f446b833f 0.600000000000 1452183 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": 991857, "vin": [ { "gen": { "height": 991847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aeb9a4e7cc7bc3e6785a2c301788d953a3832a77330a75a2745cf9f446b833f" } } ], "extra": [ 1, 84, 147, 28, 246, 238, 20, 96, 60, 192, 77, 207, 168, 70, 176, 194, 58, 230, 240, 76, 141, 212, 106, 134, 91, 43, 76, 160, 29, 165, 39, 99, 249, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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