← previous blocknext block →recent activity
Analyzing
Block #89,736,178
11 transactions · 10 stateful · 2026-07-23 21:16:51 UTC
Parallelism
45/100
Blocked
50%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,736,178 · 11 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xfe390f5b…42d9
0x34b655…2a6f
6 touches
3 conflicts
0x73320e64…b06f
0x34b655…2a6f
4 touches
1 conflict
0x8d4c0bb9…ccd3
0x34b655…2a6f
4 touches
1 conflict
0x9a8840ee…9b27
0x34b655…2a6f
4 touches
1 conflict
0x9fe82ab3…218f
0x34b655…2a6f
4 touches
1 conflict
0xa24365bc…5064
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity