Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e98d55a25bdf804b87b9858333777a98ccc1f410b6c3a83d95e3898822844a

Tx prefix hash: 1770c70dcbe1b8cd308bda85fc508d9850169fb2e4ee3f74d9f911f8d7efc9bb
Tx public key: ab807100f88dabf4432e8c53e3af7aafb3332486ecb148694fb748dda3a18e94
Timestamp: 1751841654 Timestamp [UCT]: 2025-07-06 22:40:54 Age [y:d:h:m:s]: 00:130:12:04:47
Block: 1320221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91672 RingCT/type: yes/0
Extra: 01ab807100f88dabf4432e8c53e3af7aafb3332486ecb148694fb748dda3a18e94021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb42b4afc22a9ba706fa718ca202bb0d5ae4e20454746d720fa88fe3d59160ff 0.600000000000 1807918 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": 1320231, "vin": [ { "gen": { "height": 1320221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb42b4afc22a9ba706fa718ca202bb0d5ae4e20454746d720fa88fe3d59160ff" } } ], "extra": [ 1, 171, 128, 113, 0, 248, 141, 171, 244, 67, 46, 140, 83, 227, 175, 122, 175, 179, 51, 36, 134, 236, 177, 72, 105, 79, 183, 72, 221, 163, 161, 142, 148, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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