Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a10a52a4137e48b268c2aaccc943465660c9c44de22e37c034775d91cd31b33

Tx prefix hash: 9db466afe4c795a350e1c6eedd6f5d1b5d39cde1629160495847f0ced1ede0e4
Tx public key: 5b7120e62e392e306d331354bfb1730a21d5f6e574a479e2ba19959d2cd217ae
Timestamp: 1728325561 Timestamp [UCT]: 2024-10-07 18:26:01 Age [y:d:h:m:s]: 01:044:04:56:11
Block: 1126575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289981 RingCT/type: yes/0
Extra: 015b7120e62e392e306d331354bfb1730a21d5f6e574a479e2ba19959d2cd217ae021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83b39f979f9e24283ff5effb0ca585c314f5736f063ed55f456dfe2ef56d39d4 0.600000000000 1609370 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": 1126585, "vin": [ { "gen": { "height": 1126575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83b39f979f9e24283ff5effb0ca585c314f5736f063ed55f456dfe2ef56d39d4" } } ], "extra": [ 1, 91, 113, 32, 230, 46, 57, 46, 48, 109, 51, 19, 84, 191, 177, 115, 10, 33, 213, 246, 229, 116, 164, 121, 226, 186, 25, 149, 157, 44, 210, 23, 174, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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