Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d343fcd4c91f21d6bd7bd4ec4987315d3ba26884888d98600748fb99d0d4a53b

Tx prefix hash: f921fd37d09c6274fdd4d142536c7fdadd8672f974903930f30a842f5f8e35a2
Tx public key: f4a4d257083f1d0e16192b9dd9447029e9e13b9eb5d4e5201534540c3175adbe
Timestamp: 1693095715 Timestamp [UCT]: 2023-08-27 00:21:55 Age [y:d:h:m:s]: 01:265:15:50:24
Block: 834670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451042 RingCT/type: yes/0
Extra: 01f4a4d257083f1d0e16192b9dd9447029e9e13b9eb5d4e5201534540c3175adbe02110000000633af99f4000000000000000000

1 output(s) for total of 1.052971529000 dcy

stealth address amount amount idx
00: 4e171373920a028444b005919243d955e123c5a9e1dc64395ed32c73fdb6105f 1.052971529000 1287178 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": 834680, "vin": [ { "gen": { "height": 834670 } } ], "vout": [ { "amount": 1052971529, "target": { "key": "4e171373920a028444b005919243d955e123c5a9e1dc64395ed32c73fdb6105f" } } ], "extra": [ 1, 244, 164, 210, 87, 8, 63, 29, 14, 22, 25, 43, 157, 217, 68, 112, 41, 233, 225, 59, 158, 181, 212, 229, 32, 21, 52, 84, 12, 49, 117, 173, 190, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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