← previous blocknext block →recent activity

Analyzing

Block #86,155,091

26 transactions · 23 stateful · 2026-07-07 08:19:52 UTC

Parallelism

88/100

Blocked

26%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,155,091  ·  26 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x77ed432f…fa04

0x065c9d…c394

4 touches
1 conflict

0x95523e2a…4c01

0x065c9d…c394

4 touches
1 conflict

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x8bffd880…ad1e

0x34b655…2a6f

4 touches
1 conflict

0xde398ff4…00ca

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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