← previous blocknext block →recent activity
Analyzing
Block #105,849,838
23 transactions · 22 stateful · 2026-09-18 09:00:15 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,849,838 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w07w111w112w213w214w115w216w317w418w522w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
10 touches
10 conflicts
0x08f265b9…0f30
0x34b655…2a6f
6 touches
3 conflicts
0x49e90d60…d8bc
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xc7b01caa…88b1
0x34b655…2a6f
6 touches
3 conflicts
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x931975c2…b7b3
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
10 conflicts on slot 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity