← previous blocknext block →recent activity
Analyzing
Block #107,816,285
20 transactions · 18 stateful · 2026-09-25 06:02:11 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,816,285 · 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
9w010w111w212w213w314w415w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0893415…913d
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
8 touches
6 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x379e77ed…b222
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
6 conflicts on slot 0xc08934157c…5c913d
Audit this contract →
← previous block·next block →recent activity