← previous blocknext block →recent activity
Analyzing
Block #107,817,090
41 transactions · 35 stateful · 2026-09-25 06:06:14 UTC
Parallelism
83/100
Blocked
34%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,817,090 · 41 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
2w05w011w013w114w115w216w317w318w419w420w521w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
14 touches
21 conflicts
0x8f2e9543…e315
0x34b655…2a6f
10 touches
10 conflicts
0x641aed07…bcb9
0x34b655…2a6f
10 touches
10 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xef2b34ac…9adc
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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
21 conflicts on slot 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity