← previous blocknext block →recent activity

Analyzing

Block #86,055,726

20 transactions · 16 stateful · 2026-07-06 21:16:48 UTC

Parallelism

90/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,055,726  ·  20 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x2f358e74…1022

0x34b655…2a6f

4 touches
1 conflict

0x8e507257…71c1

0x34b655…2a6f

4 touches
1 conflict

0xa4e88c04…603d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xd800e635…b1d7

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 0xec0e022022…becb90

← previous block·next block →recent activity