Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a86893436c7a4d23d6ff87957f620df4c5c3330f06bab765a7b2dd5b7305eb09

Tx prefix hash: b59c63fea930c3aa66894f8e1549da6d34ae374c7a8d20c2463a7a8518f63254
Tx public key: 8e50f103b6fb9864d434ec14dffc12f7eb06c08e66204e2284f831cf9f961938
Timestamp: 1712210531 Timestamp [UCT]: 2024-04-04 06:02:11 Age [y:d:h:m:s]: 01:215:08:22:49
Block: 992951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412596 RingCT/type: yes/0
Extra: 018e50f103b6fb9864d434ec14dffc12f7eb06c08e66204e2284f831cf9f96193802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bea334cbf03e3d09a6f0d731784c72fabc317f9dce0a163f4006c7c59bed58b7 0.600000000000 1453329 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": 992961, "vin": [ { "gen": { "height": 992951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bea334cbf03e3d09a6f0d731784c72fabc317f9dce0a163f4006c7c59bed58b7" } } ], "extra": [ 1, 142, 80, 241, 3, 182, 251, 152, 100, 212, 52, 236, 20, 223, 252, 18, 247, 235, 6, 192, 142, 102, 32, 78, 34, 132, 248, 49, 207, 159, 150, 25, 56, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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