← previous blocknext block →recent activity
Analyzing
Block #91,446,294
37 transactions · 30 stateful · 2026-07-29 21:05:25 UTC
Parallelism
73/100
Blocked
67%
Avg conflicts / tx
1.49
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,446,294 · 37 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w48w19w111w014w115w216w317w018w128w531w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x308ce62e…9e6a
0xd32edf…ff58
11 touches
15 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x48cba2…b48b
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x51134e2a…e079
0x34b655…2a6f
4 touches
1 conflict
0x5cc78005…4877
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity