Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 949bd0bde6623465d007a44399c40d9cf4c1b035f24a57ddd07060fa1aa77eba

Tx prefix hash: a12006b8c327c0f410679cee48e4f265e52a45b8b1256efb009ca0f81585b46e
Tx public key: 825c0e5ff58282ae7fc4bf895f65f7650160f6284c2f153cd5dec84aa67ea30c
Timestamp: 1763318037 Timestamp [UCT]: 2025-11-16 18:33:57 Age [y:d:h:m:s]: 00:051:17:47:30
Block: 1413553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37056 RingCT/type: yes/0
Extra: 01825c0e5ff58282ae7fc4bf895f65f7650160f6284c2f153cd5dec84aa67ea30c021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c680c465a8e99b347e4bc724230bf253a998a806e65de31083c800e26aa8312 0.600000000000 1902032 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": 1413563, "vin": [ { "gen": { "height": 1413553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c680c465a8e99b347e4bc724230bf253a998a806e65de31083c800e26aa8312" } } ], "extra": [ 1, 130, 92, 14, 95, 245, 130, 130, 174, 127, 196, 191, 137, 95, 101, 247, 101, 1, 96, 246, 40, 76, 47, 21, 60, 213, 222, 200, 74, 166, 126, 163, 12, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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