← previous blocknext block →recent activity

Analyzing

Block #86,322,872

17 transactions · 15 stateful · 2026-07-08 03:00:12 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,322,872  ·  17 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

6 touches
3 conflicts

0x72c59202…701b

0x34b655…2a6f

6 touches
3 conflicts

0x830b63a6…8105

0x34b655…2a6f

6 touches
3 conflicts

0x96dd83e6…a507

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x4755fafb…859b

0x34b655…2a6f

4 touches
1 conflict

0x559447b0…eb51

0x34b655…2a6f

4 touches
1 conflict

0x56f8cb3d…1b66

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity