← previous blocknext block →recent activity
Analyzing
Block #92,580,264
12 transactions · 12 stateful · 2026-08-02 20:09:14 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,580,264 · 12 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
2w05w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb61c96d1…424b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x3c3621c7…3e11
0x34b655…2a6f
2 touches
0 conflicts
0x4a99ba46…452f
0x34b655…2a6f
2 touches
0 conflicts
0x6323c5ea…ce8a
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 0xb61c96d126…56424b
Audit this contract →
← previous block·next block →recent activity