Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 714fc8655e13f3f4499452050c39ad66db54a0895d4f091048288ca8ffdf5473

Tx prefix hash: ad4fa3b57ef1a5c2c64c61ce3d1b799412089eea6165ae7e284ab0aecbac0ada
Tx public key: 4aafc71e775d85e5b61a3cc0e62d231bd5d9ec4787e97749f85f0afbd3e6373b
Timestamp: 1762439661 Timestamp [UCT]: 2025-11-06 14:34:21 Age [y:d:h:m:s]: 00:047:01:48:50
Block: 1406260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33711 RingCT/type: yes/0
Extra: 014aafc71e775d85e5b61a3cc0e62d231bd5d9ec4787e97749f85f0afbd3e6373b021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eae640f9b178f12c12640d87a06e3d6ce2fb824bc4696570c8a3d392526edd5 0.600000000000 1894643 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": 1406270, "vin": [ { "gen": { "height": 1406260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eae640f9b178f12c12640d87a06e3d6ce2fb824bc4696570c8a3d392526edd5" } } ], "extra": [ 1, 74, 175, 199, 30, 119, 93, 133, 229, 182, 26, 60, 192, 230, 45, 35, 27, 213, 217, 236, 71, 135, 233, 119, 73, 248, 95, 10, 251, 211, 230, 55, 59, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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