← previous blocknext block →recent activity
Analyzing
Block #107,816,538
11 transactions · 11 stateful · 2026-09-25 06:03:27 UTC
Parallelism
28/100
Blocked
64%
Avg conflicts / tx
1.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,816,538 · 11 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
2w03w14w25w36w47w58w69w010w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdd97c21…e3d0
0x34b655…2a6f
12 touches
15 conflicts
0x4cd7fdf4…7197
0x34b655…2a6f
10 touches
10 conflicts
0xf51ec09c…b4a9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x4f87784c…3a83
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0xbdd97c213f…cee3d0
Audit this contract →
← previous block·next block →recent activity