← previous blocknext block →recent activity
Analyzing
Block #91,961,567
17 transactions · 16 stateful · 2026-07-31 16:17:38 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,961,567 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w28w39w410w511w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a5ced1c…3b29
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x02991b41…19e6
0x34b655…2a6f
6 touches
3 conflicts
0x4f306739…f531
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
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
6 conflicts on slot 0x8a5ced1cae…443b29
Audit this contract →
← previous block·next block →recent activity