← previous blocknext block →recent activity

Analyzing

Block #86,443,979

24 transactions · 16 stateful · 2026-07-08 16:29:09 UTC

Parallelism

83/100

Blocked

44%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,443,979  ·  24 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

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xb6ed530c…d450

0x34b655…2a6f

6 touches
3 conflicts

0x616c7c23…14e7

0x34b655…2a6f

4 touches
1 conflict

0x90e113f8…c8f9

0xc8689a…ee79

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x4caf91f9…8ab5

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

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 0xfaef08b108…f90696

← previous block·next block →recent activity