← previous blocknext block →recent activity
Analyzing
Block #92,484,284
13 transactions · 11 stateful · 2026-08-02 12:06:32 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,484,284 · 13 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9874e36…beed
0x34b655…2a6f
4 touches
1 conflict
0x9c1a0106…de12
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1fd19887…8e0e
0x34b655…2a6f
2 touches
0 conflicts
0x56b4b003…a9f5
0x34b655…2a6f
2 touches
0 conflicts
0x56b4b003…a9f6
0x34b655…2a6f
2 touches
0 conflicts
0x5ddfc90a…de81
0x34b655…2a6f
2 touches
0 conflicts
0x646a0293…c3e2
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 0xf9874e3690…90beed
Audit this contract →
← previous block·next block →recent activity