← previous blocknext block →recent activity
Analyzing
Block #89,855,664
9 transactions · 9 stateful · 2026-07-24 07:19:51 UTC
Parallelism
56/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,855,664 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff8fb7ba…30cc
0x34b655…2a6f
6 touches
3 conflicts
0x388633a0…86cd
0x34b655…2a6f
4 touches
1 conflict
0x5338cd99…280b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x88d3cee8…8011
0x0c65a0…0852
2 touches
0 conflicts
0x1a56da6a…78e6
0x34b655…2a6f
2 touches
0 conflicts
0x29856edf…841b
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
3 conflicts on slot 0xff8fb7ba4b…2c30cc
Audit this contract →
← previous block·next block →recent activity