← previous blocknext block →recent activity
Analyzing
Block #91,100,516
17 transactions · 17 stateful · 2026-07-28 16:03:38 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
2.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,100,516 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w39w410w511w612w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
16 touches
28 conflicts
0x705ab4ae…0162
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0xdbb47f5a…2f8e
0x34b655…2a6f
6 touches
3 conflicts
0xdb15a5dd…dbf6
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity