← previous blocknext block →recent activity
Analyzing
Block #89,736,730
16 transactions · 15 stateful · 2026-07-23 21:19:39 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,736,730 · 16 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61e01cd0…b73f
0x34b655…2a6f
4 touches
1 conflict
0x7cfaa7fb…cb12
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73e
0x34b655…2a6f
4 touches
1 conflict
0x50c16ec6…4f00
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
2 touches
0 conflicts
0x72301398…03aa
0x34b655…2a6f
2 touches
0 conflicts
0x93813fd8…2e96
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 0x61e01cd0f3…74b73f
Audit this contract →
← previous block·next block →recent activity