← previous blocknext block →recent activity
Analyzing
Block #91,442,831
22 transactions · 18 stateful · 2026-07-29 20:48:00 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,442,831 · 22 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
2w03w19w010w113w014w115w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x1346ac01…31f2
0x34b655…2a6f
4 touches
1 conflict
0x162ee430…31c3
0x34b655…2a6f
4 touches
1 conflict
0x177f8108…ff11
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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