← previous blocknext block →recent activity
Analyzing
Block #106,923,892
19 transactions · 17 stateful · 2026-09-22 03:07:59 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,923,892 · 19 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
1w02w16w07w18w29w311w212w413w514w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8590b692…b267
0x34b655…2a6f
10 touches
10 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x681b1d0d…2e6b
0x34b655…2a6f
8 touches
6 conflicts
0x81696049…331c
0x34b655…2a6f
8 touches
6 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a850
0x1b6862…e19c
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 0x8590b69238…6ab267
Audit this contract →
← previous block·next block →recent activity