Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 704165a914d1c0520e996a55e5f2bd22b7063b5407b8b65ac2bd36a53a7c92da

Tx prefix hash: 396112dbb1e4ee90e471470196be26ab292ee6930b24b4b9b9582a118088d201
Tx public key: 8e301b489d0c106e4bb0c054d6ad16976d4bc69db9201c6fa0c9d1a7323643a0
Timestamp: 1730168211 Timestamp [UCT]: 2024-10-29 02:16:51 Age [y:d:h:m:s]: 01:095:02:28:28
Block: 1141800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326294 RingCT/type: yes/0
Extra: 018e301b489d0c106e4bb0c054d6ad16976d4bc69db9201c6fa0c9d1a7323643a0021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bc0d116cbec0c19ca586cec7813f2d03f969d4393d078dc67345ae07e4c4319 0.600000000000 1625629 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": 1141810, "vin": [ { "gen": { "height": 1141800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bc0d116cbec0c19ca586cec7813f2d03f969d4393d078dc67345ae07e4c4319" } } ], "extra": [ 1, 142, 48, 27, 72, 157, 12, 16, 110, 75, 176, 192, 84, 214, 173, 22, 151, 109, 75, 198, 157, 185, 32, 28, 111, 160, 201, 209, 167, 50, 54, 67, 160, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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