← previous blocknext block →recent activity
Analyzing
Block #91,445,874
20 transactions · 19 stateful · 2026-07-29 21:03:18 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,445,874 · 20 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
1w02w13w25w06w17w28w39w411w513w617w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fa2d1bd…0221
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe4cd050f…fafc
0x34b655…2a6f
6 touches
3 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
6 touches
3 conflicts
0x08a39015…efa0
0x34b655…2a6f
6 touches
3 conflicts
0x72083f0d…082a
0x34b655…2a6f
6 touches
3 conflicts
0x48f72d9d…f95f
0xd32edf…ff58
5 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
15 conflicts on slot 0x2fa2d1bd1d…710221
Audit this contract →
← previous block·next block →recent activity