← previous blocknext block →recent activity
Analyzing
Block #91,903,418
34 transactions · 30 stateful · 2026-07-31 11:25:08 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #91,903,418 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w39w110w011w112w413w514w615w719w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd18e4cb7…88d4
0x34b655…2a6f
6 touches
3 conflicts
0xc3780c0f…31e0
0x34b655…2a6f
6 touches
3 conflicts
0xb444b9b5…9c7b
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity