← previous blocknext block →recent activity

Analyzing

Block #89,770,750

19 transactions · 18 stateful · 2026-07-24 00:11:29 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

0.79

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #89,770,750  ·  19 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

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x4acbdbcf…a8c6

0x34b655…2a6f

6 touches
3 conflicts

0x5b37bb6b…aaff

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x7f63a266…68c0

0x34b655…2a6f

6 touches
3 conflicts

0x276e06d4…3958

0x34b655…2a6f

4 touches
1 conflict

0x5f394770…ac95

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 0x326a02b5c5…5c8dad

← previous block·next block →recent activity