← previous blocknext block →recent activity

Analyzing

Block #85,457,949

22 transactions · 20 stateful · 2026-07-04 02:52:33 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,457,949  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x180a50ad…95bf

0xd32edf…ff58

7 touches
6 conflicts

0x513a16ac…f8ed

0x34b655…2a6f

6 touches
3 conflicts

0xa20a130c…5d59

0x34b655…2a6f

6 touches
3 conflicts

0xafb2524a…0ce4

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity