← previous blocknext block →recent activity
Analyzing
Block #89,860,895
13 transactions · 11 stateful · 2026-07-24 07:46:10 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,860,895 · 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
4w06w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac5cfb4e…bb6e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3343d6f…bbdf
0x34b655…2a6f
4 touches
1 conflict
0xacfd8774…87ec
0x34b655…2a6f
4 touches
1 conflict
0xc516fef7…841c
0x34b655…2a6f
4 touches
1 conflict
0xd309d3a4…cb85
0x34b655…2a6f
4 touches
1 conflict
0xed6d5e8f…b410
0x34b655…2a6f
4 touches
1 conflict
0xf3343d6f…bbde
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 0xac5cfb4e33…acbb6e
Audit this contract →
← previous block·next block →recent activity