Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d49f638c53e5222f6716e43a854d9b14d83cf4862a0f1831b14bfaab73450e14

Tx prefix hash: 048fdf51df77b530dca3fa3de147074aa8d75859002042e62fed875fbfd217af
Tx public key: f417e2a62b685f04f49b542c985a8690d7ef144adae72e7edab95fb3a0e9b2d9
Timestamp: 1761284797 Timestamp [UCT]: 2025-10-24 05:46:37 Age [y:d:h:m:s]: 00:060:09:01:48
Block: 1396720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43204 RingCT/type: yes/0
Extra: 01f417e2a62b685f04f49b542c985a8690d7ef144adae72e7edab95fb3a0e9b2d9021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d1b461d8c2a10fc579a99f2bc5b6e3393d725463455674d2f8dede2ead80803 0.600000000000 1885007 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": 1396730, "vin": [ { "gen": { "height": 1396720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d1b461d8c2a10fc579a99f2bc5b6e3393d725463455674d2f8dede2ead80803" } } ], "extra": [ 1, 244, 23, 226, 166, 43, 104, 95, 4, 244, 155, 84, 44, 152, 90, 134, 144, 215, 239, 20, 74, 218, 231, 46, 126, 218, 185, 95, 179, 160, 233, 178, 217, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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