← previous blocknext block →recent activity
Analyzing
Block #107,816,188
21 transactions · 20 stateful · 2026-09-25 06:01:42 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,816,188 · 21 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
1w07w010w111w212w313w114w415w516w619w720w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a0b926a…1b4b
0x34b655…2a6f
12 touches
15 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
12 touches
15 conflicts
0xb1616aa9…771c
0x34b655…2a6f
10 touches
10 conflicts
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
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
15 conflicts on slot 0x2a0b926a6b…1f1b4b
Audit this contract →
← previous block·next block →recent activity