← previous blocknext block →recent activity
Analyzing
Block #107,817,102
17 transactions · 17 stateful · 2026-09-25 06:06:18 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,817,102 · 17 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
5w07w08w19w210w311w412w513w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
12 touches
15 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
12 touches
15 conflicts
0x93e9d6dc…6aea
0x34b655…2a6f
12 touches
15 conflicts
0x641aed07…bcb9
0x34b655…2a6f
10 touches
10 conflicts
0x8041f328…97e7
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xef2b34ac…9adc
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
15 conflicts on slot 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity