Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa98308880c6654f895796f850b8e5c30259ff2dd91c34497d8fc4d6dab4fc77

Tx prefix hash: f6cb50daf25477570534c9dd8adf574aef137ed29055c5eea7abeb78d2a6241d
Tx public key: 2514118999ae9fbe9a12fc8b82aef83bce2dca21f2a3a767a08c8cc74962d47d
Timestamp: 1697084263 Timestamp [UCT]: 2023-10-12 04:17:43 Age [y:d:h:m:s]: 01:112:21:42:55
Block: 867777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341690 RingCT/type: yes/0
Extra: 012514118999ae9fbe9a12fc8b82aef83bce2dca21f2a3a767a08c8cc74962d47d0211000000014b8f5122000000000000000000

1 output(s) for total of 0.817889435000 dcy

stealth address amount amount idx
00: b12e220d2257c9212148a79a1914cebbc3f635d2a3335ed2e9c25d86a7ce9f71 0.817889435000 1322493 of 0

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": 867787, "vin": [ { "gen": { "height": 867777 } } ], "vout": [ { "amount": 817889435, "target": { "key": "b12e220d2257c9212148a79a1914cebbc3f635d2a3335ed2e9c25d86a7ce9f71" } } ], "extra": [ 1, 37, 20, 17, 137, 153, 174, 159, 190, 154, 18, 252, 139, 130, 174, 248, 59, 206, 45, 202, 33, 242, 163, 167, 103, 160, 140, 140, 199, 73, 98, 212, 125, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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