← previous blocknext block →recent activity
Analyzing
Block #89,691,564
17 transactions · 16 stateful · 2026-07-23 17:31:45 UTC
Parallelism
53/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #89,691,564 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w18w29w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca7791f6…ab44
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x1b39afc7…4e44
0x34b655…2a6f
4 touches
1 conflict
0x23953bde…4c8c
0x34b655…2a6f
4 touches
1 conflict
0x28504822…ded6
0x34b655…2a6f
4 touches
1 conflict
0x35b89cd8…5092
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity