Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b95442d298de21bee6dfca3821603791fb6fb5a089c0c163a8de95b03805db5

Tx prefix hash: 546c1b211f1112032decc83bb8667676182c5c4a2c072b927ee27c493b0db737
Tx public key: e17c306410b85729adfbc6d90e37477f91959acf86b3465e61f515d71260c8f4
Timestamp: 1745754659 Timestamp [UCT]: 2025-04-27 11:50:59 Age [y:d:h:m:s]: 00:014:01:28:52
Block: 1270565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10052 RingCT/type: yes/0
Extra: 01e17c306410b85729adfbc6d90e37477f91959acf86b3465e61f515d71260c8f40211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb2f4b375d55f4f14c269a4ca79fb11fdc33924139d0fb621f971de67d8a12e0 0.600000000000 1757808 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": 1270575, "vin": [ { "gen": { "height": 1270565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb2f4b375d55f4f14c269a4ca79fb11fdc33924139d0fb621f971de67d8a12e0" } } ], "extra": [ 1, 225, 124, 48, 100, 16, 184, 87, 41, 173, 251, 198, 217, 14, 55, 71, 127, 145, 149, 154, 207, 134, 179, 70, 94, 97, 245, 21, 215, 18, 96, 200, 244, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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