← previous blocknext block →recent activity
Analyzing
Block #106,542,128
25 transactions · 25 stateful · 2026-09-20 19:05:32 UTC
Parallelism
60/100
Blocked
64%
Avg conflicts / tx
2.16
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,542,128 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w38w413w414w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf600d332…44c3
0x34b655…2a6f
16 touches
28 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
14 touches
21 conflicts
0xa2bc9923…3304
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
8 touches
6 conflicts
0x2d071de0…c86e
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
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
28 conflicts on slot 0xf600d33208…2b44c3
Audit this contract →
← previous block·next block →recent activity