← previous blocknext block →recent activity
Analyzing
Block #89,850,266
11 transactions · 11 stateful · 2026-07-24 06:52:42 UTC
Parallelism
45/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,850,266 · 11 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x392f42be…733c
0x34b655…2a6f
4 touches
1 conflict
0x3a4fcecc…478c
0x34b655…2a6f
4 touches
1 conflict
0x3bab4355…fbfd
0x34b655…2a6f
4 touches
1 conflict
0x575b141f…0cef
0x34b655…2a6f
4 touches
1 conflict
0x59037442…7fd5
0x34b655…2a6f
4 touches
1 conflict
0x5edb8bbe…bc75
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
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 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity