Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce7d658a45bb8cc05cd65eabf88a7ade3ce53b434705b945018e53ae48c04954

Tx prefix hash: 00fa71603ae8543d548df840c22c4e6a09f61243945cfe57fdf386b4fd8096ac
Tx public key: 018f1cbdf61695bfdeaf0653a5739c6314c3e3a7e158a2763371db659c5dc665
Timestamp: 1759996763 Timestamp [UCT]: 2025-10-09 07:59:23 Age [y:d:h:m:s]: 00:075:16:17:58
Block: 1386026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54181 RingCT/type: yes/0
Extra: 01018f1cbdf61695bfdeaf0653a5739c6314c3e3a7e158a2763371db659c5dc665021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa68bfd4a7cd5d2c017f3294fde84a11cbd4ed5d9d9dd9d5ec9b8a38896b15b4 0.600000000000 1874189 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": 1386036, "vin": [ { "gen": { "height": 1386026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa68bfd4a7cd5d2c017f3294fde84a11cbd4ed5d9d9dd9d5ec9b8a38896b15b4" } } ], "extra": [ 1, 1, 143, 28, 189, 246, 22, 149, 191, 222, 175, 6, 83, 165, 115, 156, 99, 20, 195, 227, 167, 225, 88, 162, 118, 51, 113, 219, 101, 156, 93, 198, 101, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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