← previous blocknext block →recent activity
Analyzing
Block #106,539,124
20 transactions · 20 stateful · 2026-09-20 18:50:25 UTC
Parallelism
60/100
Blocked
45%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,539,124 · 20 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
1w02w04w05w16w27w310w014w115w116w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x57e5abc1…286f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xdad20621…06b1
0x34b655…2a6f
8 touches
6 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
6 touches
3 conflicts
0x886db264…846e
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity