← previous blocknext block →recent activity
Analyzing
Block #91,097,930
14 transactions · 13 stateful · 2026-07-28 15:50:37 UTC
Parallelism
50/100
Blocked
46%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,097,930 · 14 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
3w04w18w29w310w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedf2c231…d5e4
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
6 touches
3 conflicts
0x709c2293…6c55
0x34b655…2a6f
4 touches
1 conflict
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0xbd9491f7…dd92
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 0xedf2c2312e…11d5e4
Audit this contract →
← previous block·next block →recent activity