← previous blocknext block →recent activity
Analyzing
Block #106,958,418
28 transactions · 28 stateful · 2026-09-22 06:01:47 UTC
Parallelism
75/100
Blocked
57%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,958,418 · 28 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
1w02w13w24w05w17w09w010w111w212w313w214w415w516w617w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x09e11877…85c2
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x63bc8147…dd42
0x34b655…2a6f
8 touches
6 conflicts
0x8590b692…b267
0x34b655…2a6f
8 touches
6 conflicts
0x58e06bab…34d1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
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 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity