← previous blocknext block →recent activity
Analyzing
Block #91,089,903
29 transactions · 24 stateful · 2026-07-28 15:10:13 UTC
Parallelism
72/100
Blocked
46%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,089,903 · 29 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
5w09w112w013w114w015w116w217w318w419w520w621w726w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0xce06a0f7…efef
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xbde524f4…43bf
0x34b655…2a6f
16 touches
28 conflicts
0x5256b248…5624
0x34b655…2a6f
9 touches
10 conflicts
0x69b2bb01…a032
0x34b655…2a6f
9 touches
10 conflicts
0x6f0906cb…c7e5
0x34b655…2a6f
6 touches
3 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
6 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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity