Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b62feec89330da058431d531fc478059dcf648c04cb40cd9a33cd6c29163c379

Tx prefix hash: 9e2f91470a7ea64a231eb360c8a6356a8ad59e2691f8fc581fef0fd1a5e071e8
Tx public key: c2e706e289c741000b2b1dd394280eaf3ffc9a23aa6f3ba2120fafa7138a3dba
Timestamp: 1700458052 Timestamp [UCT]: 2023-11-20 05:27:32 Age [y:d:h:m:s]: 02:050:17:10:36
Block: 895538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556096 RingCT/type: yes/0
Extra: 01c2e706e289c741000b2b1dd394280eaf3ffc9a23aa6f3ba2120fafa7138a3dba021100000001679a8a81000000000000000000

1 output(s) for total of 0.661775737000 dcy

stealth address amount amount idx
00: 164aa85dc37b6210445115cdfbf25765df0304d754afff38816d1441b1f5c101 0.661775737000 1351775 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": 895548, "vin": [ { "gen": { "height": 895538 } } ], "vout": [ { "amount": 661775737, "target": { "key": "164aa85dc37b6210445115cdfbf25765df0304d754afff38816d1441b1f5c101" } } ], "extra": [ 1, 194, 231, 6, 226, 137, 199, 65, 0, 11, 43, 29, 211, 148, 40, 14, 175, 63, 252, 154, 35, 170, 111, 59, 162, 18, 15, 175, 167, 19, 138, 61, 186, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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