Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89d12e54dbe0cfbdf9aa7fccb067df3716307f2151b2c03ab04b08b43809978

Tx prefix hash: 34e43c92852fbe4a1eec266f304c13053b0070daef1cb2f2d6f4aaadf6fac474
Tx public key: a426bd0e1d22162bd8071419f5e67996c5315e7b01546931d39e04b98987d254
Timestamp: 1736127203 Timestamp [UCT]: 2025-01-06 01:33:23 Age [y:d:h:m:s]: 00:090:05:01:27
Block: 1191129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64249 RingCT/type: yes/0
Extra: 01a426bd0e1d22162bd8071419f5e67996c5315e7b01546931d39e04b98987d2540211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02b233943af1e810ca58a56fff7e262967f3d7349c31faaa276902a4aa90018f 0.600000000000 1677652 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": 1191139, "vin": [ { "gen": { "height": 1191129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02b233943af1e810ca58a56fff7e262967f3d7349c31faaa276902a4aa90018f" } } ], "extra": [ 1, 164, 38, 189, 14, 29, 34, 22, 43, 216, 7, 20, 25, 245, 230, 121, 150, 197, 49, 94, 123, 1, 84, 105, 49, 211, 158, 4, 185, 137, 135, 210, 84, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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