← previous blocknext block →recent activity
Analyzing
Block #91,257,107
20 transactions · 19 stateful · 2026-07-29 05:11:27 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,257,107 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w211w312w213w318w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a9450c3…e1bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xd3406c63…f416
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x799082f0…5976
0x40c49f…2af0
4 touches
1 conflict
0xc579d48d…6b05
0x40c49f…2af0
4 touches
1 conflict
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
3 conflicts on slot 0x9a9450c3e3…2be1bf
Audit this contract →
← previous block·next block →recent activity