Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02fc5d3fbae3fb4b3b43ba0603a722a4fb57d979ef3dd6085e77bef8f1634b19

Tx prefix hash: 8aa1a2523accf6d3442c88032a5c2ff401aa4527807b910689dfd38b5ae3ee05
Tx public key: 0a439f6640b00bd1ab825605525cda31603d259746cbd335b1eca0be772ef6d7
Timestamp: 1730203189 Timestamp [UCT]: 2024-10-29 11:59:49 Age [y:d:h:m:s]: 00:157:23:52:20
Block: 1142087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112743 RingCT/type: yes/0
Extra: 010a439f6640b00bd1ab825605525cda31603d259746cbd335b1eca0be772ef6d70211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0483fb6c7ad2475d0c8e4ad36d9cfa4c5e06653a0dd47759f29c28eb66f0441 0.600000000000 1625924 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": 1142097, "vin": [ { "gen": { "height": 1142087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0483fb6c7ad2475d0c8e4ad36d9cfa4c5e06653a0dd47759f29c28eb66f0441" } } ], "extra": [ 1, 10, 67, 159, 102, 64, 176, 11, 209, 171, 130, 86, 5, 82, 92, 218, 49, 96, 61, 37, 151, 70, 203, 211, 53, 177, 236, 160, 190, 119, 46, 246, 215, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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