← previous blocknext block →recent activity
Analyzing
Block #91,130,914
11 transactions · 9 stateful · 2026-07-28 18:36:32 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,130,914 · 11 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
3w04w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x1c3295fd…097a
0x34b655…2a6f
6 touches
3 conflicts
0xa922f1c0…7881
0x34b655…2a6f
6 touches
3 conflicts
0x70b7b52e…7743
0x34b655…2a6f
6 touches
3 conflicts
0x70b7b52e…7744
0x34b655…2a6f
6 touches
3 conflicts
0xa2197c7e…bd47
0x34b655…2a6f
4 touches
1 conflict
0xa779293b…5e59
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity