← previous blocknext block →recent activity
Analyzing
Block #91,097,326
83 transactions · 57 stateful · 2026-07-28 15:47:35 UTC
Parallelism
76/100
Blocked
75%
Avg conflicts / tx
2.17
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #91,097,326 · 83 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w16w07w18w29w311w215w323w626w456w357w758w859w968w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0x5502e1cc…3910
0x34b655…2a6f
12 touches
15 conflicts
0x0d622e34…0000
0x681e90…ae09
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 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