← previous blocknext block →recent activity
Analyzing
Block #89,667,264
9 transactions · 9 stateful · 2026-07-23 15:28:27 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,667,264 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43fd3667…094b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0xfb8c6cf4…01ee
0x34b655…2a6f
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
2 touches
0 conflicts
0x0aa283ae…ef9c
0x34b655…2a6f
2 touches
0 conflicts
0x183c10a3…2e0a
0x34b655…2a6f
2 touches
0 conflicts
0x2e53e3a8…5dd7
0x34b655…2a6f
2 touches
0 conflicts
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 0x43fd366775…d0094b
Audit this contract →
← previous block·next block →recent activity