← previous blocknext block →recent activity
Analyzing
Block #89,689,072
13 transactions · 12 stateful · 2026-07-23 17:19:10 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,689,072 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa42c4f4c…038b
0x0a2fbf…29b1
4 touches
1 conflict
0xa42c4f4c…038c
0x0a2fbf…29b1
4 touches
1 conflict
0xc5515c28…f661
0x0a2fbf…29b1
4 touches
1 conflict
0xc5515c28…f662
0x0a2fbf…29b1
4 touches
1 conflict
0xc5515c28…f665
0x0a2fbf…29b1
4 touches
1 conflict
0x021622a8…54cf
0x34b655…2a6f
4 touches
1 conflict
0x47e40776…b54d
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity