← previous blocknext block →recent activity
Analyzing
Block #107,817,095
17 transactions · 17 stateful · 2026-09-25 06:06:16 UTC
Parallelism
53/100
Blocked
65%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,817,095 · 17 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
1w02w13w26w37w08w19w210w311w412w513w615w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5cf4d55d…c588
0x34b655…2a6f
10 touches
10 conflicts
0x641aed07…bcb9
0x34b655…2a6f
8 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0x49570407…8583
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x9b334941…fde1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x42522e76…2592
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
10 conflicts on slot 0x5cf4d55d39…13c588
Audit this contract →
← previous block·next block →recent activity