← previous blocknext block →recent activity

Analyzing

Block #89,376,375

17 transactions · 14 stateful · 2026-07-22 07:22:01 UTC

Parallelism

82/100

Blocked

14%

Avg conflicts / tx

0.12

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #89,376,375  ·  17 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf9d8ca45…db17

0x34b655…2a6f

4 touches
1 conflict

0x2d94ecd9…43db

0x34b655…2a6f

4 touches
1 conflict

0x6fe7d366…78ff

0x34b655…2a6f

4 touches
1 conflict

0x805d08cf…3cfc

0x34b655…2a6f

4 touches
1 conflict

0xf1cc9519…84c1

0x34b655…2a6f

4 touches
1 conflict

0x48b13e5e…3c2a

0x34b655…2a6f

2 touches
0 conflicts

0x51053335…4157

0x34b655…2a6f

2 touches
0 conflicts

0x539ecb5b…871b

0x34b655…2a6f

2 touches
0 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: Perpl

1 conflict on slot 0xf9d8ca454c…58db17

← previous block·next block →recent activity