Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d535881f3097dbf99abec1af0af94c87dac7e7ffb42a7b2e0f1dbb31438e7b

Tx prefix hash: a342c0435bee5626d7c14a5dc6d934c63bece84a1f3f06521cd78288f8002e04
Tx public key: 77763d24e78745013f096051e60bde93ddba04a3e3cda8857d98d5e93e26bf42
Timestamp: 1576928468 Timestamp [UTC]: 2019-12-21 11:41:08 Age [y:d:h:m:s]: 06:335:03:00:51
Block: 29347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1652605 RingCT/type: yes/0
Extra: 0177763d24e78745013f096051e60bde93ddba04a3e3cda8857d98d5e93e26bf420211000000179159db1e000000000000000000

1 output(s) for total of 0.490639003619 xmr

stealth address amount amount idx tag
00: 0e59cbcd2b1a2354f2dfd7d16f58b4b5a65203932bfc9b396cc367906119546d 0.490639003619 48179 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": 29357, "vin": [ { "gen": { "height": 29347 } } ], "vout": [ { "amount": 490639003619, "target": { "key": "0e59cbcd2b1a2354f2dfd7d16f58b4b5a65203932bfc9b396cc367906119546d" } } ], "extra": [ 1, 119, 118, 61, 36, 231, 135, 69, 1, 63, 9, 96, 81, 230, 11, 222, 147, 221, 186, 4, 163, 227, 205, 168, 133, 125, 152, 213, 233, 62, 38, 191, 66, 2, 17, 0, 0, 0, 23, 145, 89, 219, 30, 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: