← previous blocknext block →recent activity

Analyzing

Block #89,674,541

23 transactions · 18 stateful · 2026-07-23 16:05:40 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #89,674,541  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8218911e…3bed

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0725ad1d…a03f

0x34b655…2a6f

4 touches
1 conflict

0x09924b4d…d104

0x34b655…2a6f

4 touches
1 conflict

0x0a57a2b8…3cdd

0x34b655…2a6f

4 touches
1 conflict

0x1b49ab69…bfc5

0x34b655…2a6f

4 touches
1 conflict

0x5ea9eca9…22a6

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 0xc824469a90…af6425

← previous block·next block →recent activity