← previous blocknext block →recent activity

Analyzing

Block #89,785,884

23 transactions · 20 stateful · 2026-07-24 01:27:52 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,785,884  ·  23 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa3a621f8…75a2

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x6f1a10f8…5a04

0x34b655…2a6f

6 touches
3 conflicts

0x0f2d78b1…7363

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0xd6289e73…4276

0x34b655…2a6f

6 touches
3 conflicts

0xb15e92da…72fe

0x34b655…2a6f

6 touches
3 conflicts

0x33967383…de4d

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0xa3a621f8f3…6975a2

← previous block·next block →recent activity