← previous blocknext block →recent activity
Analyzing
Block #91,386,003
16 transactions · 15 stateful · 2026-07-29 16:00:51 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
1.69
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,386,003 · 16 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
2w03w04w17w28w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0xf3d10975…0d07
0x34b655…2a6f
12 touches
15 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0xfb2e822f…0cd7
0x34b655…2a6f
5 touches
3 conflicts
0x44825bf9…bf85
0x34b655…2a6f
5 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
5 touches
3 conflicts
0xe7527590…16d2
0x34b655…2a6f
5 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 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity