Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47f99e8dd73bee3c9c16ade12f4d01c7acacd894f436504d99b8dcef23b1b0a1

Tx prefix hash: 1854a59544244cc998cfa20c02c13c71cf5ff0a0cdd8a4a9615bd5f5e67046b7
Tx public key: 1429a0d484ff40e88234076df06c40e5ede6a9533128d3895e10d33c2fcd05bd
Timestamp: 1685783702 Timestamp [UCT]: 2023-06-03 09:15:02 Age [y:d:h:m:s]: 01:223:09:31:24
Block: 774129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421081 RingCT/type: yes/0
Extra: 011429a0d484ff40e88234076df06c40e5ede6a9533128d3895e10d33c2fcd05bd02110000000133af99f4000000000000000000

1 output(s) for total of 1.671049961000 dcy

stealth address amount amount idx
00: 6a2ae767568bcfc36d9f05df7772bcb8ecb2c52a8373084960369b7455c0e0cb 1.671049961000 1223592 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": 774139, "vin": [ { "gen": { "height": 774129 } } ], "vout": [ { "amount": 1671049961, "target": { "key": "6a2ae767568bcfc36d9f05df7772bcb8ecb2c52a8373084960369b7455c0e0cb" } } ], "extra": [ 1, 20, 41, 160, 212, 132, 255, 64, 232, 130, 52, 7, 109, 240, 108, 64, 229, 237, 230, 169, 83, 49, 40, 211, 137, 94, 16, 211, 60, 47, 205, 5, 189, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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