← previous blocknext block →recent activity
Analyzing
Block #91,395,240
17 transactions · 17 stateful · 2026-07-29 16:47:19 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,395,240 · 17 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
5w07w18w210w312w313w414w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0xbc66586e…20fe
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
6 touches
3 conflicts
0x6e6b8ec7…2197
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0xa4ef0838…cb54
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity