Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93a064087938e0dbe3a513de0540dd00d5448a9b9e391c92d3446ec659c013f4

Tx prefix hash: 1fb369ddac75bec2b691320a8f1f6eedcec7eed59902d5130857bb44b853149c
Tx public key: a9c714e83f34240914d65861a8b5e5094800737750f580c47a78050c0e6ed026
Timestamp: 1713740195 Timestamp [UCT]: 2024-04-21 22:56:35 Age [y:d:h:m:s]: 01:259:02:46:03
Block: 1005648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443929 RingCT/type: yes/0
Extra: 01a9c714e83f34240914d65861a8b5e5094800737750f580c47a78050c0e6ed0260211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ed7021a851ed09cbea8b29b6f6e25f619a159d87d198d26e49b43c0b2c639ee 0.600000000000 1466406 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": 1005658, "vin": [ { "gen": { "height": 1005648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ed7021a851ed09cbea8b29b6f6e25f619a159d87d198d26e49b43c0b2c639ee" } } ], "extra": [ 1, 169, 199, 20, 232, 63, 52, 36, 9, 20, 214, 88, 97, 168, 181, 229, 9, 72, 0, 115, 119, 80, 245, 128, 196, 122, 120, 5, 12, 14, 110, 208, 38, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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