← previous blocknext block →recent activity
Analyzing
Block #89,596,171
15 transactions · 15 stateful · 2026-07-23 07:50:32 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,596,171 · 15 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
5w06w19w210w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa04baf40…bbb5
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x92145e19…6904
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x7985b1c9…9c1d
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x8a1713b7…9411
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
6 conflicts on slot 0xa04baf404e…38bbb5
Audit this contract →
← previous block·next block →recent activity