← previous blocknext block →recent activity
Analyzing
Block #91,104,811
18 transactions · 17 stateful · 2026-07-28 16:25:14 UTC
Parallelism
50/100
Blocked
47%
Avg conflicts / tx
1.5
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #91,104,811 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w210w313w414w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x57be321f…fecc
0x34b655…2a6f
8 touches
6 conflicts
0xff3d6184…43dd
0x34b655…2a6f
8 touches
6 conflicts
0x53a7111b…8897
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
8 touches
6 conflicts
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0x6fbc2e5a…e69c
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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity