← previous blocknext block →recent activity

Analyzing

Block #89,379,251

20 transactions · 19 stateful · 2026-07-22 07:41:16 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #89,379,251  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xadd9c687…1f8b

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

6 touches
3 conflicts

0x508bbf1b…fe95

0x34b655…2a6f

6 touches
3 conflicts

0x30e3f228…0d43

0x34b655…2a6f

4 touches
1 conflict

0x333c820d…10c1

0x34b655…2a6f

4 touches
1 conflict

0x553d09ad…e640

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 0xadd9c68757…a51f8b

← previous block·next block →recent activity