← previous blocknext block →recent activity

Analyzing

Block #86,319,101

17 transactions · 15 stateful · 2026-07-08 02:35:00 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0xca2926e0…61b5

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xac8b9dbe…1039

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5318

0x34b655…2a6f

4 touches
1 conflict

0x842389d2…e6ea

0x34b655…2a6f

4 touches
1 conflict

0x89999c15…fdac

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 0xca2926e0af…1961b5

← previous block·next block →recent activity