Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baeb48e8255a03753476b42d55d82f30b83dd12bc64e0960d83a6d29ffe186be

Tx prefix hash: f93c2b08b2dba88b27f8b83a7d3ef7fbe3460df11147f4b6bfe769c76b5c8c93
Tx public key: db27bea421351d193f9fd15cdfd5dbb40b26527414120f24f8e9ba5c643bad09
Timestamp: 1738143050 Timestamp [UCT]: 2025-01-29 09:30:50 Age [y:d:h:m:s]: 01:000:00:17:30
Block: 1207555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258551 RingCT/type: yes/0
Extra: 01db27bea421351d193f9fd15cdfd5dbb40b26527414120f24f8e9ba5c643bad090211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab7a4877a21b098e1bc50ecfc985c5c80762262ca46b45915d5a91298763d63b 0.600000000000 1694280 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": 1207565, "vin": [ { "gen": { "height": 1207555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab7a4877a21b098e1bc50ecfc985c5c80762262ca46b45915d5a91298763d63b" } } ], "extra": [ 1, 219, 39, 190, 164, 33, 53, 29, 25, 63, 159, 209, 92, 223, 213, 219, 180, 11, 38, 82, 116, 20, 18, 15, 36, 248, 233, 186, 92, 100, 59, 173, 9, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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