← previous blocknext block →recent activity
Analyzing
Block #106,242,191
27 transactions · 27 stateful · 2026-09-19 17:56:02 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,242,191 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w17w29w010w111w212w314w415w516w617w718w826w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f140f9f…405c
0x34b655…2a6f
16 touches
28 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x3cf50d44…961b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x7f140f9f3a…64405c
Audit this contract →
← previous block·next block →recent activity