← previous blocknext block →recent activity
Analyzing
Block #91,104,854
20 transactions · 19 stateful · 2026-07-28 16:25:27 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,104,854 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w310w211w312w113w414w317w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
10 touches
10 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xcc58c80b…ff79
0x34b655…2a6f
8 touches
6 conflicts
0x7bb8bdfc…f677
0x34b655…2a6f
6 touches
3 conflicts
0x421099c9…8896
0x34b655…2a6f
6 touches
3 conflicts
0x9cfd1d07…9b43
0x34b655…2a6f
4 touches
1 conflict
0xb6225cbd…94e1
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
10 conflicts on slot 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity