← previous blocknext block →recent activity
Analyzing
Block #89,666,226
17 transactions · 17 stateful · 2026-07-23 15:23:10 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,666,226 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w17w211w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x04e17b28…d9ef
0x34b655…2a6f
4 touches
1 conflict
0x3cd4fa0e…3092
0x34b655…2a6f
4 touches
1 conflict
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
4 touches
1 conflict
0x72ae3a67…d306
0x34b655…2a6f
4 touches
1 conflict
0x99c5409a…25b7
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