Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c49d5e7ce44bea50732161b4972ff583c7416241673c79d383f6e89d591dc0f

Tx prefix hash: ce5f22bb1f505594cbcb165214d1a257592d6ee649d8078aed118ae32ae20d56
Tx public key: f82458aa17ec8f4380030b52d3387de0ee442e200aa73ad86bd2e5ce0a2ca6c7
Timestamp: 1755777981 Timestamp [UCT]: 2025-08-21 12:06:21 Age [y:d:h:m:s]: 00:084:21:28:03
Block: 1351270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60591 RingCT/type: yes/0
Extra: 01f82458aa17ec8f4380030b52d3387de0ee442e200aa73ad86bd2e5ce0a2ca6c7021100000008b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f64e93092a4b1441538e8924eb600b76d27d727beb21d9c11aa10c7683bc1f 0.600000000000 1839221 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": 1351280, "vin": [ { "gen": { "height": 1351270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f64e93092a4b1441538e8924eb600b76d27d727beb21d9c11aa10c7683bc1f" } } ], "extra": [ 1, 248, 36, 88, 170, 23, 236, 143, 67, 128, 3, 11, 82, 211, 56, 125, 224, 238, 68, 46, 32, 10, 167, 58, 216, 107, 210, 229, 206, 10, 44, 166, 199, 2, 17, 0, 0, 0, 8, 178, 247, 132, 196, 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