← previous blocknext block →recent activity
Analyzing
Block #106,110,069
21 transactions · 19 stateful · 2026-09-19 06:50:59 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,110,069 · 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
1w02w13w24w05w16w17w212w213w314w415w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4d37162…967c
0x34b655…2a6f
10 touches
10 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x16867f4f…0bb3
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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 0xa4d371626a…aa967c
Audit this contract →
← previous block·next block →recent activity