← previous blocknext block →recent activity
Analyzing
Block #89,577,156
13 transactions · 11 stateful · 2026-07-23 05:43:35 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,577,156 · 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
1w02w13w04w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd192f4ed…d7ec
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x85dc2524…53bc
0x754704…b603
4 touches
1 conflict
0x90942247…f5cb
0x754704…b603
4 touches
1 conflict
0xc9b0e68e…a55a
0x754704…b603
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x69d0a300…67ef
0x34b655…2a6f
4 touches
1 conflict
0x7ccb4355…c3e2
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
1 conflict on slot 0xd192f4edae…03d7ec
Audit this contract →
← previous block·next block →recent activity