← previous blocknext block →recent activity
Analyzing
Block #92,483,083
22 transactions · 18 stateful · 2026-08-02 12:00:30 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.77
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,483,083 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w010w211w315w417w518w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdeb02fe5…8e82
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x68a2902c…b23f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xcffc17bc…3544
0x34b655…2a6f
6 touches
3 conflicts
0x70a7b5d6…fe0e
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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 0xdeb02fe5c4…838e82
Audit this contract →
← previous block·next block →recent activity