← previous blocknext block →recent activity
Analyzing
Block #89,703,076
17 transactions · 11 stateful · 2026-07-23 18:29:45 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,703,076 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x006c3b86…59a9
0x34b655…2a6f
4 touches
1 conflict
0x02a26238…fcc3
0x34b655…2a6f
4 touches
1 conflict
0x18778ae2…d4f4
0x34b655…2a6f
4 touches
1 conflict
0x236ec88d…d4a9
0x34b655…2a6f
4 touches
1 conflict
0x2d9d808e…85ae
0x34b655…2a6f
4 touches
1 conflict
0x41bd2e6b…e240
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c848
0x34b655…2a6f
4 touches
1 conflict
0x438268c2…c849
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 0x006c3b8659…7a59a9
Audit this contract →
← previous block·next block →recent activity