← previous blocknext block →recent activity
Analyzing
Block #89,515,604
14 transactions · 14 stateful · 2026-07-22 22:52:27 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,515,604 · 14 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
2w05w06w08w110w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35def84a…0327
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x731f2745…9370
0xa6afd3…d132
4 touches
1 conflict
0xf1cc9519…84c1
0x34b655…2a6f
4 touches
1 conflict
0x28c62bca…b746
0x34b655…2a6f
2 touches
0 conflicts
0x4755fafb…859b
0x34b655…2a6f
2 touches
0 conflicts
0x58620f29…db5a
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 0x35def84adc…f90327
Audit this contract →
← previous block·next block →recent activity