Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ca2d9ac279375688286b3fe5d8deaf737784c83cc8dbfad7bcf4bc43996e92e

Tx prefix hash: f5c24a04fab9a8e47e603c04b06af88b8fffcd45f0545762840d820637b895e5
Tx public key: 8b19709f609c71a1e93d47f9a7c0dca13699a1474674d0f320b3738403f7c7dc
Timestamp: 1748146003 Timestamp [UCT]: 2025-05-25 04:06:43 Age [y:d:h:m:s]: 00:178:22:08:41
Block: 1290364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125573 RingCT/type: yes/0
Extra: 018b19709f609c71a1e93d47f9a7c0dca13699a1474674d0f320b3738403f7c7dc0211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ad87a4ec3a7c3b261f4110bfa7ccea4386401a92d00f5c50a59011cfa46fcc5 0.600000000000 1777833 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": 1290374, "vin": [ { "gen": { "height": 1290364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ad87a4ec3a7c3b261f4110bfa7ccea4386401a92d00f5c50a59011cfa46fcc5" } } ], "extra": [ 1, 139, 25, 112, 159, 96, 156, 113, 161, 233, 61, 71, 249, 167, 192, 220, 161, 54, 153, 161, 71, 70, 116, 208, 243, 32, 179, 115, 132, 3, 247, 199, 220, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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