← previous blocknext block →recent activity
Analyzing
Block #92,568,826
12 transactions · 12 stateful · 2026-08-02 19:11:42 UTC
Parallelism
33/100
Blocked
58%
Avg conflicts / tx
2.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,568,826 · 12 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xea4eae68…9828
0x34b655…2a6f
6 touches
3 conflicts
0x9e15e7b9…9fdf
0x34b655…2a6f
6 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
5 touches
3 conflicts
0xb415dca6…5bdd
0x34b655…2a6f
4 touches
1 conflict
0x2ca3a7a0…e60d
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
28 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity