← previous blocknext block →recent activity
Analyzing
Block #107,848,691
18 transactions · 18 stateful · 2026-09-25 08:45:17 UTC
Parallelism
61/100
Blocked
39%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,848,691 · 18 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
6w07w08w19w210w311w412w513w615w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf75c3a6b…0568
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x92132ed7…2722
0x34b655…2a6f
6 touches
3 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
6 touches
3 conflicts
0x46e288ff…5f7e
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xba522812…1f1f
0x34b655…2a6f
6 touches
3 conflicts
0x790c39b8…c45a
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 0xf75c3a6bf5…da0568
Audit this contract →
← previous block·next block →recent activity