← previous blocknext block →recent activity
Analyzing
Block #89,518,931
13 transactions · 13 stateful · 2026-07-22 23:14:40 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,518,931 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba059816…a847
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0x1941b441…5889
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0xba0598166c…b0a847
Audit this contract →
← previous block·next block →recent activity