← previous blocknext block →recent activity
Analyzing
Block #91,111,365
15 transactions · 15 stateful · 2026-07-28 16:58:12 UTC
Parallelism
47/100
Blocked
47%
Avg conflicts / tx
1.87
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,111,365 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x705ab4ae…0162
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x720ae293…6a10
0x34b655…2a6f
7 touches
6 conflicts
0x94de4d05…ad01
0x34b655…2a6f
6 touches
3 conflicts
0xe0b0cc71…9f6a
0x34b655…2a6f
5 touches
3 conflicts
0x1eec2e88…9f1c
0x34b655…2a6f
5 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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity