← previous blocknext block →recent activity
Analyzing
Block #107,848,241
20 transactions · 20 stateful · 2026-09-25 08:43:01 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,848,241 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35ff5a2e…3ccd
0x34b655…2a6f
8 touches
6 conflicts
0xf75c3a6b…0568
0x34b655…2a6f
8 touches
6 conflicts
0xdeaa385f…6b8b
0x34b655…2a6f
8 touches
6 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
8 touches
6 conflicts
0xbe44c40d…bd08
0x34b655…2a6f
8 touches
6 conflicts
0x93afca4c…b47f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x42522e76…2592
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
6 conflicts on slot 0x35ff5a2eac…fd3ccd
Audit this contract →
← previous block·next block →recent activity