← previous blocknext block →recent activity
Analyzing
Block #106,477,088
23 transactions · 20 stateful · 2026-09-20 13:38:11 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,477,088 · 23 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
1w02w13w04w15w16w212w213w314w315w416w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x377b5b72…73d4
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0x911aed91…3a82
0x34b655…2a6f
8 touches
6 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
8 touches
6 conflicts
0xaaef622a…65b7
0x34b655…2a6f
8 touches
6 conflicts
0xbaf6ed88…c179
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0x377b5b72d7…1173d4
Audit this contract →
← previous block·next block →recent activity