← previous blocknext block →recent activity
Analyzing
Block #91,434,410
15 transactions · 14 stateful · 2026-07-29 20:05:38 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,434,410 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w19w110w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xd0cd3305…f212
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a9e2858…a685
0x34b655…2a6f
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity