← previous blocknext block →recent activity
Analyzing
Block #106,567,589
21 transactions · 21 stateful · 2026-09-20 21:13:40 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
1.24
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,567,589 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w09w111w212w313w414w515w016w217w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76e87dc3…612b
0x34b655…2a6f
12 touches
15 conflicts
0xe3d6e227…4da5
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0xe796f8b7…ad55
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 0x76e87dc3a4…a9612b
Audit this contract →
← previous block·next block →recent activity