← previous blocknext block →recent activity
Analyzing
Block #91,190,618
19 transactions · 13 stateful · 2026-07-28 23:36:53 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #91,190,618 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w112w013w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd06cc746…27e4
0x384275…7777
4 touches
1 conflict
0x40e2d65d…2a35
0x3bd359…433a
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0ace5b6a…16f9
0x34b655…2a6f
4 touches
1 conflict
0xa262abe3…19e6
0x34b655…2a6f
3 touches
1 conflict
0x705ab4ae…0162
0x34b655…2a6f
3 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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity