← previous blocknext block →recent activity
Analyzing
Block #89,380,141
13 transactions · 12 stateful · 2026-07-22 07:47:13 UTC
Parallelism
62/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,380,141 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xef1de905…0582
0x34b655…2a6f
4 touches
1 conflict
0x2e869b10…ce11
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa47b7766…ee6e
0x34b655…2a6f
4 touches
1 conflict
0x30ded6ec…3424
0x34b655…2a6f
2 touches
0 conflicts
0xde1fb60f…e5c5
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity