← previous blocknext block →recent activity
Analyzing
Block #89,773,671
11 transactions · 10 stateful · 2026-07-24 00:26:14 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,773,671 · 11 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
1w02w03w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8218911e…3bed
0x34b655…2a6f
4 touches
1 conflict
0x1050fef5…54e5
0x34b655…2a6f
2 touches
0 conflicts
0x255b063d…15d1
0x34b655…2a6f
2 touches
0 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
2 touches
0 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
2 touches
0 conflicts
0x6530927f…68be
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