← previous blocknext block →recent activity
Analyzing
Block #91,162,225
19 transactions · 18 stateful · 2026-07-28 21:14:03 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,162,225 · 19 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
1w02w14w06w07w18w29w010w111w312w413w517w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x9b6bb245…1bf8
0x34b655…2a6f
6 touches
3 conflicts
0xff3d6184…43dd
0x34b655…2a6f
6 touches
3 conflicts
0xa90a0083…2a64
0x34b655…2a6f
5 touches
3 conflicts
0x705ab4ae…0162
0x34b655…2a6f
5 touches
3 conflicts
0xac2a0273…721b
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity