← previous blocknext block →recent activity

Analyzing

Block #86,483,999

16 transactions · 14 stateful · 2026-07-08 20:56:59 UTC

Parallelism

75/100

Blocked

50%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,483,999  ·  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

0x01a08f7d…dec6

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x23778a1f…dec4

0x34b655…2a6f

8 touches
6 conflicts

0x2a534eb4…1642

0x34b655…2a6f

8 touches
6 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

8 touches
6 conflicts

0xba4d47a9…0d84

0x34b655…2a6f

8 touches
6 conflicts

0xe727ab72…768b

0x34b655…2a6f

8 touches
6 conflicts

0xeb4f35f5…3a65

0x34b655…2a6f

8 touches
6 conflicts

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 0x01a08f7dea…2ddec6

← previous block·next block →recent activity