← previous blocknext block →recent activity
Analyzing
Block #91,209,937
41 transactions · 33 stateful · 2026-07-29 01:14:03 UTC
Parallelism
66/100
Blocked
70%
Avg conflicts / tx
2.1
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,209,937 · 41 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w210w011w112w213w314w415w518w121w322w223w524w326w427w532w633w737w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
10 touches
10 conflicts
0xefcdf197…96a2
0x34b655…2a6f
10 touches
10 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
8 touches
6 conflicts
0x89678d1b…463e
0xa6afd3…d132
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity