← previous blocknext block →recent activity
Analyzing
Block #91,129,101
24 transactions · 22 stateful · 2026-07-28 18:27:25 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.63
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,129,101 · 24 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
3w04w16w07w18w211w212w313w415w516w618w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9baf16…df37
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xe58e492a…f5c5
0x34b655…2a6f
10 touches
10 conflicts
0xd676e291…3ecf
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
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
21 conflicts on slot 0xbe9baf16a9…e6df37
Audit this contract →
← previous block·next block →recent activity