← previous blocknext block →recent activity
Analyzing
Block #91,984,241
22 transactions · 21 stateful · 2026-07-31 18:11:40 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1.27
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,984,241 · 22 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
1w02w14w25w38w39w410w511w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0d3a786…91d9
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xdcccd149…4cab
0x34b655…2a6f
7 touches
6 conflicts
0xdc8d7edd…8a03
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2b648bb8…aade
0x34b655…2a6f
6 touches
3 conflicts
0xd2cb2bb3…7676
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 0xa0d3a786de…b991d9
Audit this contract →
← previous block·next block →recent activity