← previous blocknext block →recent activity

Analyzing

Block #85,619,192

20 transactions · 16 stateful · 2026-07-04 20:46:09 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,619,192  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x55a03051…2930

0x34b655…2a6f

6 touches
3 conflicts

0xef02ed46…48a4

0x34b655…2a6f

6 touches
3 conflicts

0xa7a1d036…b8aa

0x34b655…2a6f

6 touches
3 conflicts

0x178db37f…debb

0x34b655…2a6f

5 touches
3 conflicts

0x5a90c709…ce25

0xd32edf…ff58

5 touches
3 conflicts

0xb3c96942…f0fc

0x34b655…2a6f

4 touches
1 conflict

0x11431f9d…42c5

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity