← previous blocknext block →recent activity
Analyzing
Block #89,677,478
10 transactions · 9 stateful · 2026-07-23 16:20:40 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,677,478 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x536f894b…2597
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xe3e67fe3…e754
0x158622…375e
2 touches
0 conflicts
0x00f8a8f0…ceba
0x34b655…2a6f
2 touches
0 conflicts
0x183c10a3…2e0a
0x34b655…2a6f
2 touches
0 conflicts
0x2e53e3a8…5dd7
0x34b655…2a6f
2 touches
0 conflicts
0x31bae39d…e0f8
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity