← previous blocknext block →recent activity
Analyzing
Block #107,814,265
20 transactions · 18 stateful · 2026-09-25 05:52:01 UTC
Parallelism
60/100
Blocked
39%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,814,265 · 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
8w09w110w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa23b9051…392f
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x2ea3a28c…c266
0x34b655…2a6f
6 touches
3 conflicts
0xecd896e1…e453
0x34b655…2a6f
4 touches
1 conflict
0x978586e8…92a7
0x34b655…2a6f
4 touches
1 conflict
0xaa645624…7ea9
0x34b655…2a6f
4 touches
1 conflict
0xba522812…1f1f
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 0xa23b905120…88392f
Audit this contract →
← previous block·next block →recent activity