← previous blocknext block →recent activity
Analyzing
Block #107,816,844
21 transactions · 20 stateful · 2026-09-25 06:05:00 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,816,844 · 21 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
1w03w06w17w08w19w210w311w212w413w514w619w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
8 touches
6 conflicts
0x8d5fc820…1750
0x34b655…2a6f
8 touches
6 conflicts
0xb863fe3d…335f
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x4cd7fdf4…7197
0x34b655…2a6f
6 touches
3 conflicts
0xaa97569b…1480
0x34b655…2a6f
6 touches
3 conflicts
0xbdd97c21…e3d0
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 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity