Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f64927e1bdf99d97f3c46ae9d1fa41e34ea7403f2ed3ff5b1b7b2d0018d61c9f

Tx prefix hash: 813e9c766bf30aebd5d46582603ba7b2f597fffee165b9359036449707d9d239
Tx public key: c8905a09d6d1f06006a93439c26e13ec3623b8e6e6a91aeda01a3e155b4e55e4
Timestamp: 1672878365 Timestamp [UTC]: 2023-01-05 00:26:05 Age [y:d:h:m:s]: 03:051:00:14:04
Block: 667747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 816682 RingCT/type: yes/0
Extra: 01c8905a09d6d1f06006a93439c26e13ec3623b8e6e6a91aeda01a3e155b4e55e402110000000352542ceb000000000000000000

1 output(s) for total of 0.003762503864 xmr

stealth address amount amount idx tag
00: faf7924698b536f9b5ecb97adbdd9d3caba0c62b3915551d330303a597c234c8 0.003762503864 1108962 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 dinastycoin-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": 667757, "vin": [ { "gen": { "height": 667747 } } ], "vout": [ { "amount": 3762503864, "target": { "key": "faf7924698b536f9b5ecb97adbdd9d3caba0c62b3915551d330303a597c234c8" } } ], "extra": [ 1, 200, 144, 90, 9, 214, 209, 240, 96, 6, 169, 52, 57, 194, 110, 19, 236, 54, 35, 184, 230, 230, 169, 26, 237, 160, 26, 62, 21, 91, 78, 85, 228, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369