← previous blocknext block →recent activity
Analyzing
Block #91,120,049
14 transactions · 12 stateful · 2026-07-28 17:41:53 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,120,049 · 14 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
2w04w05w16w27w39w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0x520f8a31…65c5
0x34b655…2a6f
4 touches
1 conflict
0x520f8a31…65c6
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
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 0x38c6ff017b…61689f
Audit this contract →
← previous block·next block →recent activity