← previous blocknext block →recent activity

Analyzing

Block #86,448,503

22 transactions · 20 stateful · 2026-07-08 16:59:25 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,448,503  ·  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

0xee4fe1f7…3ead

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0xac6f24e7…c98b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xae8ffe10…d1bd

0x34b655…2a6f

3 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

2 touches
0 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

3 conflicts on slot 0xee4fe1f73e…483ead

← previous block·next block →recent activity