← previous blocknext block →recent activity
Analyzing
Block #106,186,034
17 transactions · 16 stateful · 2026-09-19 13:13:18 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,186,034 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w09w110w111w212w213w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24ed74ea…a3ff
0x34b655…2a6f
8 touches
6 conflicts
0x6e4184c2…f064
0x34b655…2a6f
8 touches
6 conflicts
0xd9fdc204…0e30
0x34b655…2a6f
8 touches
6 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x3195e306…7185
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
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 0x24ed74ea30…24a3ff
Audit this contract →
← previous block·next block →recent activity