Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f655d4f34cfff21e771ed011ed768c261706a839a2a60bfdcdeab104c6b12a1

Tx prefix hash: 221a9131a471a3c746e7b58acd3ffda6fc5ed8952971db69c6e901102f5dcc9c
Tx public key: c4a5c5ebeeaf87795704a325e896a2e31208330e477305fcd456024e0f4a4b7e
Timestamp: 1750932637 Timestamp [UCT]: 2025-06-26 10:10:37 Age [y:d:h:m:s]: 00:146:10:02:39
Block: 1313108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102644 RingCT/type: yes/0
Extra: 01c4a5c5ebeeaf87795704a325e896a2e31208330e477305fcd456024e0f4a4b7e0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e19d0f02d8bccb41d39022f76d6c11f643213aa4ea89008b86970c48d5a817f0 0.600000000000 1800745 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": 1313118, "vin": [ { "gen": { "height": 1313108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e19d0f02d8bccb41d39022f76d6c11f643213aa4ea89008b86970c48d5a817f0" } } ], "extra": [ 1, 196, 165, 197, 235, 238, 175, 135, 121, 87, 4, 163, 37, 232, 150, 162, 227, 18, 8, 51, 14, 71, 115, 5, 252, 212, 86, 2, 78, 15, 74, 75, 126, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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