Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b2fe983e29654fb01159640958b3034cd11ab34e7cccbaef9c75a14b53b17af

Tx prefix hash: f0bb4e671f74ed60881a13e8f240e5cc394af6695100bdb4bb4a9b84f01f7e92
Tx public key: f33f63aff695501d5b72c7edbdc3fafdd29fd5bffdd9aacdd11df0870d491687
Timestamp: 1750481754 Timestamp [UCT]: 2025-06-21 04:55:54 Age [y:d:h:m:s]: 00:146:03:56:32
Block: 1309531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102309 RingCT/type: yes/0
Extra: 01f33f63aff695501d5b72c7edbdc3fafdd29fd5bffdd9aacdd11df0870d491687021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e138d6e0e85efa2ff8d1cb03c5560ac7ae07c2139c9eb0704615c4259b39aeac 0.600000000000 1797148 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": 1309541, "vin": [ { "gen": { "height": 1309531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e138d6e0e85efa2ff8d1cb03c5560ac7ae07c2139c9eb0704615c4259b39aeac" } } ], "extra": [ 1, 243, 63, 99, 175, 246, 149, 80, 29, 91, 114, 199, 237, 189, 195, 250, 253, 210, 159, 213, 191, 253, 217, 170, 205, 209, 29, 240, 135, 13, 73, 22, 135, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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