← previous blocknext block →recent activity
Analyzing
Block #105,856,668
20 transactions · 18 stateful · 2026-09-18 09:34:38 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,856,668 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w010w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf0eb339…d417
0x34b655…2a6f
14 touches
21 conflicts
0x97e4c862…4419
0x34b655…2a6f
12 touches
15 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0x28029bbb…6bd6
0xd32edf…ff58
5 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0463db49…5d05
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
21 conflicts on slot 0xdf0eb3393a…c3d417
Audit this contract →
← previous block·next block →recent activity