← previous blocknext block →recent activity
Analyzing
Block #89,736,996
7 transactions · 6 stateful · 2026-07-23 21:20:59 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,736,996 · 7 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dcea2f…25e6
0x34b655…2a6f
4 touches
1 conflict
0x7e162301…9c1b
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x4f267385…cc89
0x34b655…2a6f
4 touches
1 conflict
0x3514c11f…5833
0x34b655…2a6f
2 touches
0 conflicts
0x4a661150…e500
0x34b655…2a6f
2 touches
0 conflicts
0x53142478…5458
0x34b655…2a6f
2 touches
0 conflicts
0x5494779e…ed9b
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 0x16dcea2fe5…b525e6
Audit this contract →
← previous block·next block →recent activity