← previous blocknext block →recent activity
Analyzing
Block #91,781,690
51 transactions · 41 stateful · 2026-07-31 01:12:40 UTC
Parallelism
63/100
Blocked
73%
Avg conflicts / tx
2.61
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #91,781,690 · 51 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w07w08w19w210w111w313w414w515w127w628w731w1033w1236w238w1142w1243w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x04c17a1b…982d
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0x93afca4c…b47e
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity