Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0d9f262b1b6c8e975fb979335730f4f65e4bfa36923e81e4114b5a26df330a4

Tx prefix hash: d7aabab35e46d226b5d9c7d259dd5f240ff0f4a6af64f8969179d399a0e33d56
Tx public key: 5911e0da1ac4e85cdb618866944b27758af38170594835bed24b25f1e1b4c070
Timestamp: 1583506439 Timestamp [UTC]: 2020-03-06 14:53:59 Age [y:d:h:m:s]: 06:258:20:06:04
Block: 77394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1604442 RingCT/type: yes/0
Extra: 015911e0da1ac4e85cdb618866944b27758af38170594835bed24b25f1e1b4c0700211000000054ac5aa02000000000000000000

1 output(s) for total of 0.340065319471 xmr

stealth address amount amount idx tag
00: 6233e2b4d79fc1b83e2b8960092aa1d0c381235b4303844f831e86d528f9a163 0.340065319471 142469 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": 77404, "vin": [ { "gen": { "height": 77394 } } ], "vout": [ { "amount": 340065319471, "target": { "key": "6233e2b4d79fc1b83e2b8960092aa1d0c381235b4303844f831e86d528f9a163" } } ], "extra": [ 1, 89, 17, 224, 218, 26, 196, 232, 92, 219, 97, 136, 102, 148, 75, 39, 117, 138, 243, 129, 112, 89, 72, 53, 190, 210, 75, 37, 241, 225, 180, 192, 112, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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) | monero version: