← previous blocknext block →recent activity

Analyzing

Block #86,319,355

22 transactions · 20 stateful · 2026-07-08 02:36:42 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,319,355  ·  22 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd1a8b9bd…6f8c

0x34b655…2a6f

4 touches
1 conflict

0xd99b3b64…1c95

0x34b655…2a6f

4 touches
1 conflict

0x03fb27fd…0c06

0x34b655…2a6f

4 touches
1 conflict

0x30b2fed1…0b2f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6f58168d…ea24

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