← previous blocknext block →recent activity
Analyzing
Block #89,675,346
22 transactions · 20 stateful · 2026-07-23 16:09:48 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,675,346 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w09w110w011w112w013w216w217w320w021w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x446f2734…8b54
0x0a3323…0a3c
4 touches
1 conflict
0x52c63247…ce02
0x0a3323…0a3c
4 touches
1 conflict
0x6fe7d366…78ff
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity