Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 806bcb434c9789765a449ea1c3e0cd2df877de3b6c53672c9dfaedbd3bcb9929

Tx prefix hash: b01546f3eb7b7ae203308ae5b23976881057ba1410fa0e0d9595be566376932a
Tx public key: 0dee73592a002ee9063ae04654bb06afb3abc6a42965e77001aab8acb31f053c
Timestamp: 1581983887 Timestamp [UTC]: 2020-02-17 23:58:07 Age [y:d:h:m:s]: 06:279:09:23:35
Block: 67071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1616423 RingCT/type: yes/0
Extra: 010dee73592a002ee9063ae04654bb06afb3abc6a42965e77001aab8acb31f053c02110000000b4ac5aa02000000000000000000

1 output(s) for total of 0.367931306388 xmr

stealth address amount amount idx tag
00: fd814a8f20d1d510b96fbea7a31c90aa69b59d473dfee0985f9f4f5dff7489f4 0.367931306388 123568 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": 67081, "vin": [ { "gen": { "height": 67071 } } ], "vout": [ { "amount": 367931306388, "target": { "key": "fd814a8f20d1d510b96fbea7a31c90aa69b59d473dfee0985f9f4f5dff7489f4" } } ], "extra": [ 1, 13, 238, 115, 89, 42, 0, 46, 233, 6, 58, 224, 70, 84, 187, 6, 175, 179, 171, 198, 164, 41, 101, 231, 112, 1, 170, 184, 172, 179, 31, 5, 60, 2, 17, 0, 0, 0, 11, 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: