← previous blocknext block →recent activity
Analyzing
Block #106,952,086
16 transactions · 16 stateful · 2026-09-22 05:29:54 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,952,086 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w18w29w211w312w414w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f887fbb…76d5
0x34b655…2a6f
10 touches
10 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
6 touches
3 conflicts
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x8590b692…b267
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 0x2f887fbb5a…4076d5
Audit this contract →
← previous block·next block →recent activity