← previous blocknext block →recent activity
Analyzing
Block #106,434,468
18 transactions · 16 stateful · 2026-09-20 10:03:39 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,434,468 · 18 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
1w02w13w14w211w212w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87c1cd94…e6df
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0x5a648f88…e6e0
0x34b655…2a6f
8 touches
6 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
8 touches
6 conflicts
0xc3baa205…f26e
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 0x87c1cd94da…48e6df
Audit this contract →
← previous block·next block →recent activity