← previous blocknext block →recent activity
Analyzing
Block #106,185,754
21 transactions · 19 stateful · 2026-09-19 13:11:53 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,185,754 · 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
1w02w13w04w15w16w211w212w313w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf90c6521…d8f0
0x34b655…2a6f
12 touches
15 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
12 touches
15 conflicts
0x629bd5e3…aeec
0x34b655…2a6f
12 touches
15 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0xfa4c3219…d219
0x34b655…2a6f
8 touches
6 conflicts
0x4f8b50d5…dc6a
0x34b655…2a6f
8 touches
6 conflicts
0x67a56c8b…f955
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
15 conflicts on slot 0xf90c6521bf…2dd8f0
Audit this contract →
← previous block·next block →recent activity