Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c86ca2558779c2127a5af7f85a24f0e0505f320d4a230cac4d2098f810764b

Tx prefix hash: 02e2ddc474f9069e39899780de28f8a30402d5acd3250ed4d194efd9684b9ec3
Tx public key: 857d3490782c911facb8d078e69f5d72385bea538f8cf0c2e83c6332ccec1567
Timestamp: 1717589816 Timestamp [UCT]: 2024-06-05 12:16:56 Age [y:d:h:m:s]: 00:307:06:16:45
Block: 1037579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219579 RingCT/type: yes/0
Extra: 01857d3490782c911facb8d078e69f5d72385bea538f8cf0c2e83c6332ccec1567021100000004f5ee2846000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb9d1aae6d6303f53f77b77c08f560569088bebfdf8d56c6f49bb569679e4c6 0.600000000000 1506124 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": 1037589, "vin": [ { "gen": { "height": 1037579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb9d1aae6d6303f53f77b77c08f560569088bebfdf8d56c6f49bb569679e4c6" } } ], "extra": [ 1, 133, 125, 52, 144, 120, 44, 145, 31, 172, 184, 208, 120, 230, 159, 93, 114, 56, 91, 234, 83, 143, 140, 240, 194, 232, 60, 99, 50, 204, 236, 21, 103, 2, 17, 0, 0, 0, 4, 245, 238, 40, 70, 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