← previous blocknext block →recent activity
Analyzing
Block #91,147,268
15 transactions · 13 stateful · 2026-07-28 19:58:50 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,147,268 · 15 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
5w06w08w19w210w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xff3d6184…43dd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4a4
0x34b655…2a6f
4 touches
1 conflict
0xa538ac07…fc9e
0x34b655…2a6f
4 touches
1 conflict
0xa538ac07…fc9f
0x34b655…2a6f
4 touches
1 conflict
0xb3cd6513…f0fb
0x34b655…2a6f
4 touches
1 conflict
0xbff10c32…e7ec
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity