Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f56cc912f9b877ce66a22d0876b5f50fd0c3e4db92fbdf62774713193127b6

Tx prefix hash: f82aef2e29198523545b8a537806d63ab6131955d8c8216dd8bd767213b9218e
Tx public key: 987c3f14f01bd87213df6312429cdc6cb7adf8c99d20dcf661f453d32b26edd9
Timestamp: 1750836075 Timestamp [UCT]: 2025-06-25 07:21:15 Age [y:d:h:m:s]: 00:147:20:12:22
Block: 1312365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103610 RingCT/type: yes/0
Extra: 01987c3f14f01bd87213df6312429cdc6cb7adf8c99d20dcf661f453d32b26edd902110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f99e6ed5a6a9238f6d7e2ce7fd59c4d7777e8cfaa948cf96c86fa930bfb6978 0.600000000000 1799998 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": 1312375, "vin": [ { "gen": { "height": 1312365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f99e6ed5a6a9238f6d7e2ce7fd59c4d7777e8cfaa948cf96c86fa930bfb6978" } } ], "extra": [ 1, 152, 124, 63, 20, 240, 27, 216, 114, 19, 223, 99, 18, 66, 156, 220, 108, 183, 173, 248, 201, 157, 32, 220, 246, 97, 244, 83, 211, 43, 38, 237, 217, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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