← previous blocknext block →recent activity
Analyzing
Block #89,403,149
17 transactions · 16 stateful · 2026-07-22 10:21:04 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,403,149 · 17 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
2w04w18w29w311w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58eb4e0…6b86
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e32
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e33
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
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
1 conflict on slot 0xf58eb4e00e…a46b86
Audit this contract →
← previous block·next block →recent activity