← previous blocknext block →recent activity

Analyzing

Block #89,559,275

17 transactions · 16 stateful · 2026-07-23 03:44:06 UTC

Parallelism

76/100

Blocked

56%

Avg conflicts / tx

0.88

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,559,275  ·  17 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x451a4a79…8f29

0x34b655…2a6f

4 touches
1 conflict

0x4ec199d4…e9f1

0x34b655…2a6f

4 touches
1 conflict

0x58cc7768…0af1

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 0x1941b4413e…0c5889

← previous block·next block →recent activity