← previous blocknext block →recent activity

Analyzing

Block #87,920,767

22 transactions · 19 stateful · 2026-07-15 13:06:00 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,920,767  ·  22 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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xcce4354b…3180

0x34b655…2a6f

6 touches
3 conflicts

0x55012d1a…3907

0x2b46c0…1669

4 touches
1 conflict

0xb5c4826d…bdd6

0x2b46c0…1669

4 touches
1 conflict

0xb8fccd1b…b5f2

0x2b46c0…1669

4 touches
1 conflict

0x248da771…d0c0

0x34b655…2a6f

4 touches
1 conflict

0x4e3e9abf…4621

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity