Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca43e9fbfed269ef79de6d2ec9053b63dd5ff2dde877e50e933fc492cadc17de

Tx prefix hash: aa0ea5221d233a4217eff5b89c51d908b377a1376603f68578492bb6b460daa4
Tx public key: c5151d7dedd43b03df84685c6ee4a2201bc8ec813b5ae574c6a6290f13269b8e
Timestamp: 1716124670 Timestamp [UCT]: 2024-05-19 13:17:50 Age [y:d:h:m:s]: 01:010:08:47:33
Block: 1025438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268327 RingCT/type: yes/0
Extra: 01c5151d7dedd43b03df84685c6ee4a2201bc8ec813b5ae574c6a6290f13269b8e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9820697568a7c4aef8ac041de47085def4a43e4860b4e6e0db705cf5f8beb4f 0.600000000000 1491941 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": 1025448, "vin": [ { "gen": { "height": 1025438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9820697568a7c4aef8ac041de47085def4a43e4860b4e6e0db705cf5f8beb4f" } } ], "extra": [ 1, 197, 21, 29, 125, 237, 212, 59, 3, 223, 132, 104, 92, 110, 228, 162, 32, 27, 200, 236, 129, 59, 90, 229, 116, 198, 166, 41, 15, 19, 38, 155, 142, 2, 17, 0, 0, 0, 2, 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