← previous blocknext block →recent activity
Analyzing
Block #106,235,155
32 transactions · 23 stateful · 2026-09-19 17:20:37 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
0.97
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,235,155 · 32 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w17w29w310w118w220w121w422w523w624w731w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57c64bc3…54a9
0x34b655…2a6f
14 touches
21 conflicts
0x3b6e959d…158f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0x310a7246…2dcb
0x34b655…2a6f
6 touches
3 conflicts
0x05e1eba1…6491
0x34b655…2a6f
6 touches
3 conflicts
0x8fc9c747…80f8
0x34b655…2a6f
4 touches
1 conflict
0xab981df1…2941
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 0x57c64bc312…6154a9
Audit this contract →
← previous block·next block →recent activity