← previous blocknext block →recent activity
Analyzing
Block #106,567,601
24 transactions · 22 stateful · 2026-09-20 21:13:44 UTC
Parallelism
79/100
Blocked
55%
Avg conflicts / tx
1.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,567,601 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w211w212w313w314w415w422w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba1edffb…323e
0x34b655…2a6f
10 touches
10 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x51441b31…2f72
0x34b655…2a6f
8 touches
6 conflicts
0x5d1ac445…5233
0x34b655…2a6f
8 touches
6 conflicts
0xabddccb7…221c
0x34b655…2a6f
8 touches
6 conflicts
0xb556cb60…3636
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
10 conflicts on slot 0xba1edffb42…64323e
Audit this contract →
← previous block·next block →recent activity