← previous blocknext block →recent activity
Analyzing
Block #89,849,046
13 transactions · 11 stateful · 2026-07-24 06:46:34 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,849,046 · 13 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
2w06w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x262d4253…b091
0x34b655…2a6f
2 touches
0 conflicts
0x2d58a69f…6820
0x34b655…2a6f
2 touches
0 conflicts
0x44a2c3ff…0abc
0x34b655…2a6f
2 touches
0 conflicts
0x466c9e6a…e9de
0x34b655…2a6f
2 touches
0 conflicts
0x4e2287ea…0654
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 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity