Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa223059a5cc30025919fb90738750ef6f17d7b3a29fa763db0ea5eac2dbb147

Tx prefix hash: 71ce14266b0c455840db047a7c6101db6c7ae562d0a06911fd79804f0dfdbf3e
Tx public key: 4bfd83826ce890696aa0a45e1efc1c3bbb6b2d18636fe965d42b25a4785c1815
Timestamp: 1724062684 Timestamp [UCT]: 2024-08-19 10:18:04 Age [y:d:h:m:s]: 00:234:12:39:03
Block: 1091238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167485 RingCT/type: yes/0
Extra: 014bfd83826ce890696aa0a45e1efc1c3bbb6b2d18636fe965d42b25a4785c181502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0ec6ff4f599119f82ae3de4c8069a0f0499aed3e6a82acc0786ec35167b2538 0.600000000000 1565869 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": 1091248, "vin": [ { "gen": { "height": 1091238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0ec6ff4f599119f82ae3de4c8069a0f0499aed3e6a82acc0786ec35167b2538" } } ], "extra": [ 1, 75, 253, 131, 130, 108, 232, 144, 105, 106, 160, 164, 94, 30, 252, 28, 59, 187, 107, 45, 24, 99, 111, 233, 101, 212, 43, 37, 164, 120, 92, 24, 21, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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