← previous blocknext block →recent activity
Analyzing
Block #92,300,335
20 transactions · 18 stateful · 2026-08-01 20:41:25 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,300,335 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w39w010w111w412w013w114w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x940ef645…018e
0x34b655…2a6f
8 touches
6 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x5cc477b5…1cf3
0x34b655…2a6f
6 touches
3 conflicts
0x6a62629d…5e33
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x940ef64543…89018e
Audit this contract →
← previous block·next block →recent activity