← previous blocknext block →recent activity
Analyzing
Block #92,078,280
10 transactions · 10 stateful · 2026-08-01 02:04:38 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,078,280 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x5666db7d…5dc4
0x34b655…2a6f
4 touches
1 conflict
0x24d1b62e…d6e8
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x2d3930d3…c9b8
0x34b655…2a6f
2 touches
0 conflicts
0x35a9f06c…7689
0x34b655…2a6f
2 touches
0 conflicts
0x60f63d67…5ba0
0x34b655…2a6f
2 touches
0 conflicts
0x77ea8cfe…b5c7
0x34b655…2a6f
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 0x91b0f8edc5…b76bd7
Audit this contract →
← previous block·next block →recent activity