← previous blocknext block →recent activity
Analyzing
Block #91,418,524
20 transactions · 20 stateful · 2026-07-29 18:44:50 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,418,524 · 20 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
2w03w14w27w08w110w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9711d99c…3d4c
0x34b655…2a6f
8 touches
6 conflicts
0x85a88798…f85e
0x34b655…2a6f
8 touches
6 conflicts
0x920fdd9d…09de
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xdcd5779c…9fd6
0x34b655…2a6f
6 touches
3 conflicts
0xf4ff6e8d…0427
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x1b5d2e60…99b5
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 0x9711d99cb2…583d4c
Audit this contract →
← previous block·next block →recent activity