← previous blocknext block →recent activity
Analyzing
Block #89,881,549
19 transactions · 18 stateful · 2026-07-24 09:30:03 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,881,549 · 19 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
3w04w16w07w09w111w012w113w214w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bba6aa0…e367
0x34b655…2a6f
6 touches
3 conflicts
0x6a4868a5…367e
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xef3f5637…f47c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x8aef18db…9238
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 0x3bba6aa0f0…8fe367
Audit this contract →
← previous block·next block →recent activity