Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9367f57cdc54ce80ae85a513bcef8e4fa232e602ef51cea5e6da8fb563955fe

Tx prefix hash: e9bfba2d82e6baa0a313e778cb311e65385db217de1246e5bf8d5d076a6acf7d
Tx public key: 2e8e259e980ac9e673595ae46e88f851ce3f37dab784cff5175b35b515b79f6e
Timestamp: 1754970400 Timestamp [UCT]: 2025-08-12 03:46:40 Age [y:d:h:m:s]: 00:138:00:20:07
Block: 1345213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97991 RingCT/type: yes/0
Extra: 012e8e259e980ac9e673595ae46e88f851ce3f37dab784cff5175b35b515b79f6e021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f44189eb534a5c5b474290b51b2ee74d899408c0dd1847a1556e3506823d21ee 0.600000000000 1833102 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": 1345223, "vin": [ { "gen": { "height": 1345213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f44189eb534a5c5b474290b51b2ee74d899408c0dd1847a1556e3506823d21ee" } } ], "extra": [ 1, 46, 142, 37, 158, 152, 10, 201, 230, 115, 89, 90, 228, 110, 136, 248, 81, 206, 63, 55, 218, 183, 132, 207, 245, 23, 91, 53, 181, 21, 183, 159, 110, 2, 17, 0, 0, 0, 1, 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