← previous blocknext block →recent activity
Analyzing
Block #91,397,690
11 transactions · 8 stateful · 2026-07-29 16:59:39 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.27
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,397,690 · 11 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
5w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53bd09d…1f7b
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd9461b7e…31bc
0x34b655…2a6f
4 touches
1 conflict
0xd411ae03…1997
0x34b655…2a6f
3 touches
1 conflict
0x703b861a…cbe4
0x188d58…ea8e
2 touches
0 conflicts
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
1 conflict on slot 0xc53bd09dc4…e01f7b
Audit this contract →
← previous block·next block →recent activity