← previous blocknext block →recent activity
Analyzing
Block #89,669,488
9 transactions · 8 stateful · 2026-07-23 15:39:50 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,669,488 · 9 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fabde5b…0629
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd330c0c5…6f64
0x34b655…2a6f
4 touches
1 conflict
0xf45f2405…c8f9
0x34b655…2a6f
4 touches
1 conflict
0x3fcb7de0…0bb1
0x34b655…2a6f
2 touches
0 conflicts
0x40bc5adc…eda6
0x34b655…2a6f
2 touches
0 conflicts
0x58a68b92…6a6e
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 0x1fabde5b84…ed0629
Audit this contract →
← previous block·next block →recent activity