← previous blocknext block →recent activity
Analyzing
Block #91,016,765
14 transactions · 14 stateful · 2026-07-28 09:02:10 UTC
Parallelism
43/100
Blocked
50%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,016,765 · 14 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
2w03w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x0f898335…7a89
0x34b655…2a6f
8 touches
6 conflicts
0x98b8e5ef…bda4
0x34b655…2a6f
8 touches
6 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x913b7808…7e04
0x34b655…2a6f
6 touches
3 conflicts
0x51428ba4…83e1
0x34b655…2a6f
6 touches
3 conflicts
0x7e17e82a…9748
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity