← previous blocknext block →recent activity

Analyzing

Block #89,404,711

13 transactions · 13 stateful · 2026-07-22 10:31:31 UTC

Parallelism

69/100

Blocked

31%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #89,404,711  ·  13 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

0x64aaadbf…f9f3

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xa3c36de0…3cf3

0x34b655…2a6f

4 touches
1 conflict

0x9cbe5c47…424b

0x34b655…2a6f

4 touches
1 conflict

0x03211df1…ca45

0x34b655…2a6f

4 touches
1 conflict

0x23c9c7bf…4e33

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x3df47518…17f8

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 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity