Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c70e1f42e52744c0879610f8ab4f2bf96aa8e290ecf119c755fcf31241e0a7df

Tx prefix hash: d74cc9fe9d8f2f919e591a3c0e34d66ac48995ae38dd52ab7a53bdd4d054e58e
Tx public key: de1c0964ff7160c14ba1802ae4d0a55733a10e798a816e94394f776f51b82486
Timestamp: 1725035994 Timestamp [UCT]: 2024-08-30 16:39:54 Age [y:d:h:m:s]: 00:240:21:52:37
Block: 1099293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172071 RingCT/type: yes/0
Extra: 01de1c0964ff7160c14ba1802ae4d0a55733a10e798a816e94394f776f51b82486021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39e10a53f6fbc49d58988ef941ca412ea0e35dd598d8b45cc100a42c9ef24dbb 0.600000000000 1575252 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": 1099303, "vin": [ { "gen": { "height": 1099293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39e10a53f6fbc49d58988ef941ca412ea0e35dd598d8b45cc100a42c9ef24dbb" } } ], "extra": [ 1, 222, 28, 9, 100, 255, 113, 96, 193, 75, 161, 128, 42, 228, 208, 165, 87, 51, 161, 14, 121, 138, 129, 110, 148, 57, 79, 119, 111, 81, 184, 36, 134, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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