← previous blocknext block →recent activity
Analyzing
Block #89,537,046
12 transactions · 11 stateful · 2026-07-23 01:15:35 UTC
Parallelism
58/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,537,046 · 12 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
3w04w16w27w38w410w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07bb3f5a…617e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb0c61571…be63
0x34b655…2a6f
6 touches
3 conflicts
0xc13e1d5c…62c6
0x34b655…2a6f
6 touches
3 conflicts
0x6e8bd807…c5bc
0x34b655…2a6f
5 touches
3 conflicts
0x63da8263…7a24
0x34b655…2a6f
4 touches
1 conflict
0x7d6b9af1…9a38
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 0x07bb3f5a12…2d617e
Audit this contract →
← previous block·next block →recent activity