← previous blocknext block →recent activity
Analyzing
Block #91,438,467
31 transactions · 29 stateful · 2026-07-29 20:26:03 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,438,467 · 31 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
1w03w04w15w26w310w011w112w213w315w317w118w320w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x92115abd…ad76
0x34b655…2a6f
8 touches
6 conflicts
0x11610d80…c9fc
0xd32edf…ff58
7 touches
6 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity