← previous blocknext block →recent activity

Analyzing

Block #86,754,942

16 transactions · 16 stateful · 2026-07-10 03:09:54 UTC

Parallelism

75/100

Blocked

25%

Avg conflicts / tx

0.31

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,754,942  ·  16 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

0xc2a783bf…25e3

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0xc3688185…9b36

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x03cf8a66…08c6

0x34b655…2a6f

4 touches
1 conflict

0x1c796c6b…064e

0x34b655…2a6f

4 touches
1 conflict

0x2d471a49…9ef8

0x34b655…2a6f

4 touches
1 conflict

0x59b0a8da…0928

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

1 conflict on slot 0xc2a783bfdf…da25e3

← previous block·next block →recent activity