← previous blocknext block →recent activity
Analyzing
Block #89,588,856
13 transactions · 12 stateful · 2026-07-23 07:01:39 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,588,856 · 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
5w06w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x536f894b…2597
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0x00966e54…7d1d
0x34b655…2a6f
4 touches
1 conflict
0x20d0c78a…d1ae
0x34b655…2a6f
4 touches
1 conflict
0x4f1ad4b4…e00a
0x34b655…2a6f
4 touches
1 conflict
0x5590b23e…869c
0x34b655…2a6f
4 touches
1 conflict
0x5612e2a1…8694
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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 0x536f894bd4…e82597
Audit this contract →
← previous block·next block →recent activity