← previous blocknext block →recent activity
Analyzing
Block #106,428,722
19 transactions · 18 stateful · 2026-09-20 09:34:43 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,428,722 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa711e6b5…6a3a
0x34b655…2a6f
12 touches
15 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
12 touches
15 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
8 touches
6 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
8 touches
6 conflicts
0xb93f1ab3…c3d9
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x5cf2d0c9…0181
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 0xa711e6b5c7…f86a3a
Audit this contract →
← previous block·next block →recent activity