← previous blocknext block →recent activity
Analyzing
Block #91,254,791
24 transactions · 23 stateful · 2026-07-29 04:59:47 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,254,791 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w111w212w013w114w217w220w221w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x41ebf7ed…f662
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50c0dd87…1128
0x34b655…2a6f
4 touches
1 conflict
0x5fa03694…de10
0x34b655…2a6f
4 touches
1 conflict
0x86d1a3fb…ed61
0x34b655…2a6f
4 touches
1 conflict
0x9bd1e2be…740d
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
3 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity