← previous blocknext block →recent activity
Analyzing
Block #92,059,939
31 transactions · 25 stateful · 2026-08-01 00:32:23 UTC
Parallelism
84/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,059,939 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w110w213w014w118w019w122w225w026w327w429w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xcff4dd72…06df
0x34b655…2a6f
6 touches
3 conflicts
0x53ef765b…e2a9
0xd32edf…ff58
5 touches
3 conflicts
0x784eaad2…d177
0x34b655…2a6f
4 touches
1 conflict
0x7b55198a…b946
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
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
10 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity