Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f20f72abe074d0589f4ecc7de73115668dd281a3d93ab05ec0f133db8035f4

Tx prefix hash: e662c0681cbdd789aeaabe7c4091ea91c8c294bda1b5646ff4aa9e9677dbe0ba
Tx public key: 742919ebcfa7289d3a3dafc89b3ea8e6289da6c6fdc618906f267fe37a24221e
Timestamp: 1744979316 Timestamp [UCT]: 2025-04-18 12:28:36 Age [y:d:h:m:s]: 00:216:19:18:25
Block: 1264146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152654 RingCT/type: yes/0
Extra: 01742919ebcfa7289d3a3dafc89b3ea8e6289da6c6fdc618906f267fe37a24221e021100000017dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f79fdb5c2c9f8c3f143b7427a367ae09a5b8c55c79c18ec9e1c5fdbd5d66c837 0.600000000000 1751341 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": 1264156, "vin": [ { "gen": { "height": 1264146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f79fdb5c2c9f8c3f143b7427a367ae09a5b8c55c79c18ec9e1c5fdbd5d66c837" } } ], "extra": [ 1, 116, 41, 25, 235, 207, 167, 40, 157, 58, 61, 175, 200, 155, 62, 168, 230, 40, 157, 166, 198, 253, 198, 24, 144, 111, 38, 127, 227, 122, 36, 34, 30, 2, 17, 0, 0, 0, 23, 219, 181, 113, 193, 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