← previous blocknext block →recent activity
Analyzing
Block #89,587,390
13 transactions · 11 stateful · 2026-07-23 06:51:53 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,587,390 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69d0a300…67ef
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x23e706b3…0e16
0x34b655…2a6f
4 touches
1 conflict
0x24555bd4…a78b
0x34b655…2a6f
4 touches
1 conflict
0x3ded0c4f…e561
0x34b655…2a6f
4 touches
1 conflict
0x5ae70cdc…6411
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
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 0x69d0a3001a…3467ef
Audit this contract →
← previous block·next block →recent activity