← previous blocknext block →recent activity
Analyzing
Block #91,761,868
17 transactions · 15 stateful · 2026-07-30 23:32:57 UTC
Parallelism
53/100
Blocked
60%
Avg conflicts / tx
2.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,761,868 · 17 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
2w03w14w05w17w28w39w410w311w512w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xfb31d278…9107
0x34b655…2a6f
8 touches
6 conflicts
0xe2e52e46…0894
0x34b655…2a6f
8 touches
6 conflicts
0xb0dd34dc…0233
0x34b655…2a6f
8 touches
6 conflicts
0x313d3d93…4aa2
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity