Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d66465ee2deb0b61e4dc9ef909fb236c3c038b00d005cb9cee014e2b4b8d5844

Tx prefix hash: 50a166a11efdf7bde0a76a7774f35d4d62b929c6096e0fe0fa3f29eabcf7fbc9
Tx public key: 9090762b84636e91aeabe4e692f54d07deb823948f8d0895f6f57f6acb3970cb
Timestamp: 1575384553 Timestamp [UTC]: 2019-12-03 14:49:13 Age [y:d:h:m:s]: 06:127:22:21:15
Block: 21563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0967 kB
Tx version: 2 No of confirmations: 1494029 RingCT/type: yes/0
Extra: 019090762b84636e91aeabe4e692f54d07deb823948f8d0895f6f57f6acb3970cb020d39303031000100000059c89603

1 output(s) for total of 0.520659388910 xmr

stealth address amount amount idx tag
00: fe2f32b62f70f0ca3c7e80a8f6047e8775e9f9409ca7f2394139ca8dbec444bc 0.520659388910 34214 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": 21573, "vin": [ { "gen": { "height": 21563 } } ], "vout": [ { "amount": 520659388910, "target": { "key": "fe2f32b62f70f0ca3c7e80a8f6047e8775e9f9409ca7f2394139ca8dbec444bc" } } ], "extra": [ 1, 144, 144, 118, 43, 132, 99, 110, 145, 174, 171, 228, 230, 146, 245, 77, 7, 222, 184, 35, 148, 143, 141, 8, 149, 246, 245, 127, 106, 203, 57, 112, 203, 2, 13, 57, 48, 48, 49, 0, 1, 0, 0, 0, 89, 200, 150, 3 ], "rct_signatures": { "type": 0 } }


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