← previous blocknext block →recent activity
Analyzing
Block #91,416,686
14 transactions · 12 stateful · 2026-07-29 18:35:35 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,416,686 · 14 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
1w06w18w29w310w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0x2dff59d9…f5e6
0x34b655…2a6f
6 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5930
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity