← previous blocknext block →recent activity
Analyzing
Block #91,438,429
30 transactions · 23 stateful · 2026-07-29 20:25:52 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,438,429 · 30 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
1w02w16w08w213w014w115w016w220w321w424w025w229w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f180f8f…1108
0x34b655…2a6f
6 touches
3 conflicts
0x92115abd…ad76
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1a3810d3…957d
0xd32edf…ff58
5 touches
3 conflicts
0x3e04662b…0da8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x3fca0fa5…0c0a
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
3 conflicts on slot 0x7f180f8f2e…661108
Audit this contract →
← previous block·next block →recent activity