Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2517009e66ab2777db2975b4cb1726453a14c260e9dcc1527de5d609234087b

Tx prefix hash: 8e3786b271eefdcf295f4aad2fed836c3b4fe209ce6ebe42f5c523747d70b843
Tx public key: 9bcd8c995b9388e3aa6f2636b59de5baefb5bb88b2c0dd46bdbcc3d24926e88b
Timestamp: 1719885687 Timestamp [UCT]: 2024-07-02 02:01:27 Age [y:d:h:m:s]: 01:133:07:13:46
Block: 1056602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353808 RingCT/type: yes/0
Extra: 019bcd8c995b9388e3aa6f2636b59de5baefb5bb88b2c0dd46bdbcc3d24926e88b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0360f231c0cdbc7bdbbfccac4090a04245b7a89d151273fdab002693befa5e2d 0.600000000000 1527017 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": 1056612, "vin": [ { "gen": { "height": 1056602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0360f231c0cdbc7bdbbfccac4090a04245b7a89d151273fdab002693befa5e2d" } } ], "extra": [ 1, 155, 205, 140, 153, 91, 147, 136, 227, 170, 111, 38, 54, 181, 157, 229, 186, 239, 181, 187, 136, 178, 192, 221, 70, 189, 188, 195, 210, 73, 38, 232, 139, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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