← previous blocknext block →recent activity
Analyzing
Block #89,744,749
24 transactions · 20 stateful · 2026-07-23 22:00:12 UTC
Parallelism
67/100
Blocked
55%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,744,749 · 24 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
2w08w09w110w211w312w413w515w116w217w520w622w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xbb322930…ace5
0x34b655…2a6f
6 touches
3 conflicts
0x5f6259bd…2f9d
0x34b655…2a6f
6 touches
3 conflicts
0x8c8907a9…abff
0xd32edf…ff58
5 touches
3 conflicts
0x749a4cb2…15f8
0x34b655…2a6f
4 touches
1 conflict
0x74b9ea61…c21c
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity