← previous blocknext block →recent activity
Analyzing
Block #89,734,621
23 transactions · 21 stateful · 2026-07-23 21:08:59 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,734,621 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w18w210w111w312w414w019w120w321w022w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb706cd78…37d8
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x01a08f7d…dec6
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb854467b…327d
0x34b655…2a6f
6 touches
3 conflicts
0xba9f9225…2ead
0x34b655…2a6f
6 touches
3 conflicts
0x8f63f383…6eda
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 0xb706cd7847…a737d8
Audit this contract →
← previous block·next block →recent activity