← previous blocknext block →recent activity
Analyzing
Block #89,680,831
10 transactions · 10 stateful · 2026-07-23 16:37:36 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,680,831 · 10 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
1w04w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dc9ce62…9b3b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
0x00958d6e…1d09
0x34b655…2a6f
2 touches
0 conflicts
0x00958d6e…1d0a
0x34b655…2a6f
2 touches
0 conflicts
0x36afc267…c157
0x34b655…2a6f
2 touches
0 conflicts
0x4118bd12…924a
0x34b655…2a6f
2 touches
0 conflicts
0x4c9e4543…6066
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 0x6dc9ce62d6…759b3b
Audit this contract →
← previous block·next block →recent activity