← previous blocknext block →recent activity
Analyzing
Block #91,098,199
23 transactions · 22 stateful · 2026-07-28 15:51:58 UTC
Parallelism
52/100
Blocked
64%
Avg conflicts / tx
2.04
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #91,098,199 · 23 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w39w310w411w512w613w714w815w916w1020w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xce06a0f7…efef
0x34b655…2a6f
16 touches
28 conflicts
0xbde524f4…43bf
0x34b655…2a6f
16 touches
28 conflicts
0xfe97c123…af37
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
36 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity