← previous blocknext block →recent activity
Analyzing
Block #89,786,757
15 transactions · 14 stateful · 2026-07-24 01:32:16 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,786,757 · 15 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
1w02w15w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xffb8950c…23c6
0x34b655…2a6f
4 touches
1 conflict
0x01076862…1db7
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xa664d878…664c
0x34b655…2a6f
4 touches
1 conflict
0xafe72ad3…c5fa
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity