← previous blocknext block →recent activity
Analyzing
Block #92,320,686
17 transactions · 15 stateful · 2026-08-01 22:23:46 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,320,686 · 17 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
2w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ff5ffda…05aa
0x34b655…2a6f
4 touches
1 conflict
0xd5ea12fa…ae5c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ceb46fa…a433
0x34b655…2a6f
2 touches
0 conflicts
0x2f426d3b…7aa9
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x40a53e5a…2fbe
0x34b655…2a6f
2 touches
0 conflicts
0x625f5c6d…4abe
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 0x4ff5ffdaa9…a205aa
Audit this contract →
← previous block·next block →recent activity