← previous blocknext block →recent activity
Analyzing
Block #105,842,222
22 transactions · 19 stateful · 2026-09-18 08:21:48 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,842,222 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w19w211w213w014w115w116w217w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x814ba1ee…5451
0x34b655…2a6f
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x814ba1eecc…dc5451
Audit this contract →
← previous block·next block →recent activity