← previous blocknext block →recent activity
Analyzing
Block #92,335,587
26 transactions · 24 stateful · 2026-08-01 23:38:42 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,335,587 · 26 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
1w02w15w09w011w112w015w216w317w419w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xc8b7d55e…1afd
0x34b655…2a6f
7 touches
6 conflicts
0x4bc1abab…5874
0x34b655…2a6f
5 touches
3 conflicts
0x5f251b96…6054
0x34b655…2a6f
4 touches
1 conflict
0xce3a759a…1620
0x34b655…2a6f
4 touches
1 conflict
0x959e17ee…0830
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
6 conflicts on slot 0xf3d10975b0…050d07
Audit this contract →
← previous block·next block →recent activity