Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3d65bbfa52539a1d2fc49ef9b92676989c8cb45dea805da795172f1db8c1d3c

Tx prefix hash: 40cf76d08576217efcbb8f890bff77d2ec907ed25fcec7a37e871abde0d61cad
Tx public key: 817c2ab22370009c665725f0b20d0a5ae9f0fdab492a2afc640cefd4cb9a3c57
Timestamp: 1715331648 Timestamp [UCT]: 2024-05-10 09:00:48 Age [y:d:h:m:s]: 01:004:05:24:10
Block: 1018860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263947 RingCT/type: yes/0
Extra: 01817c2ab22370009c665725f0b20d0a5ae9f0fdab492a2afc640cefd4cb9a3c5702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 046a3097cb9c298652035dc51430422412f5431dc3ff732baf7433d1703cfa04 0.600000000000 1482655 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": 1018870, "vin": [ { "gen": { "height": 1018860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "046a3097cb9c298652035dc51430422412f5431dc3ff732baf7433d1703cfa04" } } ], "extra": [ 1, 129, 124, 42, 178, 35, 112, 0, 156, 102, 87, 37, 240, 178, 13, 10, 90, 233, 240, 253, 171, 73, 42, 42, 252, 100, 12, 239, 212, 203, 154, 60, 87, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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