← previous blocknext block →recent activity

Analyzing

Block #89,711,191

15 transactions · 15 stateful · 2026-07-23 19:10:39 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,711,191  ·  15 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

0x00000000…0006

0x0a2fbf…29b1

6 touches
3 conflicts

0x9932c6d5…0e65

0x0a2fbf…29b1

6 touches
3 conflicts

0x9932c6d5…0e66

0x0a2fbf…29b1

6 touches
3 conflicts

0x9932c6d5…0e69

0x0a2fbf…29b1

6 touches
3 conflicts

0xbfe60507…e208

0x0a2fbf…29b1

6 touches
3 conflicts

0xbfe60507…e209

0x0a2fbf…29b1

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

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: 0x0a2fbf2d…f729b1

3 conflicts on slot 0x0000000000…000006

← previous block·next block →recent activity