← previous blocknext block →recent activity
Analyzing
Block #89,749,900
16 transactions · 13 stateful · 2026-07-23 22:26:13 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,749,900 · 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
5w06w110w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bdf3604…e56e
0x34b655…2a6f
4 touches
1 conflict
0xb2b8fbd5…88fa
0x34b655…2a6f
4 touches
1 conflict
0xcd5c0ecb…4b5f
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd4
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0x46e558af…7871
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 0x9bdf360464…a1e56e
Audit this contract →
← previous block·next block →recent activity