← previous blocknext block →recent activity
Analyzing
Block #91,016,570
26 transactions · 24 stateful · 2026-07-28 09:01:11 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,016,570 · 26 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
1w05w06w17w28w19w210w013w014w117w118w219w323w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81974778…128f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xb0608dfe…083d
0x34b655…2a6f
6 touches
3 conflicts
0x49083ad2…da7e
0xd32edf…ff58
5 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x81974778b7…b4128f
Audit this contract →
← previous block·next block →recent activity