Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855f904b4607fa67e6073c7db1012eb1f75c5212b4d8d72b5338b04384314aa9

Tx prefix hash: be5c2dbb3f9407da221d5d70b907a7d82ab7c5de2fd33f7ce3e3bcab320e8478
Tx public key: d90f51493f67e2e08e74a88fd31d40856850a38627de3d3dbf7f744ea3e3e4ad
Timestamp: 1759859942 Timestamp [UCT]: 2025-10-07 17:59:02 Age [y:d:h:m:s]: 00:090:04:44:18
Block: 1384890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64614 RingCT/type: yes/0
Extra: 01d90f51493f67e2e08e74a88fd31d40856850a38627de3d3dbf7f744ea3e3e4ad021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a9f08049a1bcd5e6ff4bb0c120c786d95e2578cbdea9949058b377dad832ed 0.600000000000 1873047 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": 1384900, "vin": [ { "gen": { "height": 1384890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a9f08049a1bcd5e6ff4bb0c120c786d95e2578cbdea9949058b377dad832ed" } } ], "extra": [ 1, 217, 15, 81, 73, 63, 103, 226, 224, 142, 116, 168, 143, 211, 29, 64, 133, 104, 80, 163, 134, 39, 222, 61, 61, 191, 127, 116, 78, 163, 227, 228, 173, 2, 17, 0, 0, 0, 3, 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