← previous blocknext block →recent activity
Analyzing
Block #92,568,011
10 transactions · 10 stateful · 2026-08-02 19:07:36 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,568,011 · 10 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
1w02w14w25w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x859fe39d…effa
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x5fd97c7b…b1fa
0x34b655…2a6f
6 touches
3 conflicts
0x67a9f76d…0b84
0x34b655…2a6f
4 touches
1 conflict
0x67a9f76d…0b85
0x34b655…2a6f
4 touches
1 conflict
0x87b36e04…4dbd
0x34b655…2a6f
4 touches
1 conflict
0x87b36e04…4dbe
0x34b655…2a6f
4 touches
1 conflict
0x8ce5fb99…20fa
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 0x859fe39d3d…7beffa
Audit this contract →
← previous block·next block →recent activity