← previous blocknext block →recent activity
Analyzing
Block #92,286,213
11 transactions · 9 stateful · 2026-08-01 19:30:24 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,286,213 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w07w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68caa37b…c795
0x34b655…2a6f
6 touches
3 conflicts
0x3204d119…c63f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x5d96a9b6…ea38
0x34b655…2a6f
4 touches
1 conflict
0x0b35df1d…7c83
0x34b655…2a6f
2 touches
0 conflicts
0x26e0a088…01f7
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
3 conflicts on slot 0x68caa37b30…f7c795
Audit this contract →
← previous block·next block →recent activity