Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ad7189094e55717ef60341b87fb60f226748de0c8ff4e41903378a5b03391d3

Tx prefix hash: a19ce283ba76160b3be91f5b02606530e0b6272fb92426f9058e0c0b84ff9bd9
Tx public key: 98c83c8f699f258d0a5582f4dc39259b6a449fa16483e33ca0f98cd8d811b47f
Timestamp: 1737277172 Timestamp [UCT]: 2025-01-19 08:59:32 Age [y:d:h:m:s]: 00:331:00:00:37
Block: 1200608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234140 RingCT/type: yes/0
Extra: 0198c83c8f699f258d0a5582f4dc39259b6a449fa16483e33ca0f98cd8d811b47f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cefd99265fbc6251ac1552750db8779e88a9f5b3c7d0fab0cf5fcc96bbc3a755 0.600000000000 1687253 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": 1200618, "vin": [ { "gen": { "height": 1200608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cefd99265fbc6251ac1552750db8779e88a9f5b3c7d0fab0cf5fcc96bbc3a755" } } ], "extra": [ 1, 152, 200, 60, 143, 105, 159, 37, 141, 10, 85, 130, 244, 220, 57, 37, 155, 106, 68, 159, 161, 100, 131, 227, 60, 160, 249, 140, 216, 216, 17, 180, 127, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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