← previous blocknext block →recent activity
Analyzing
Block #91,002,446
11 transactions · 10 stateful · 2026-07-28 07:49:51 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,002,446 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w06w17w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e4d1089…86ed
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x34904ec4…aa8b
0x34b655…2a6f
4 touches
1 conflict
0xe4b8f2c5…f54d
0x34b655…2a6f
4 touches
1 conflict
0x6e6b8ec7…2197
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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 0x6e4d1089e1…8086ed
Audit this contract →
← previous block·next block →recent activity