← previous blocknext block →recent activity
Analyzing
Block #89,405,313
14 transactions · 12 stateful · 2026-07-22 10:35:32 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,405,313 · 14 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
5w06w17w08w110w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16e0f5bc…e1d0
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0x36f92745…fbb7
0x34b655…2a6f
4 touches
1 conflict
0x45c30d46…47a5
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x584dafa2…f60d
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
6 conflicts on slot 0x16e0f5bc05…a5e1d0
Audit this contract →
← previous block·next block →recent activity