← previous blocknext block →recent activity
Analyzing
Block #107,817,068
25 transactions · 22 stateful · 2026-09-25 06:06:07 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,817,068 · 25 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
4w05w110w111w012w113w214w315w416w517w618w722w223w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
16 touches
28 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
12 touches
15 conflicts
0x641aed07…bcb9
0x34b655…2a6f
12 touches
15 conflicts
0xe6341958…a301
0x34b655…2a6f
8 touches
6 conflicts
0xb7ad89d3…c28e
0x34b655…2a6f
8 touches
6 conflicts
0x7aa6fe3e…5fb2
0xd32edf…ff58
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8041f328…97e7
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
28 conflicts on slot 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity