← previous blocknext block →recent activity
Analyzing
Block #91,290,965
23 transactions · 20 stateful · 2026-07-29 08:02:34 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,290,965 · 23 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
1w02w16w27w310w011w112w213w214w015w116w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xac8a5059…fd42
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x3f8e1a58…17a8
0xd32edf…ff58
5 touches
3 conflicts
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d2
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity