← previous blocknext block →recent activity

Analyzing

Block #86,804,705

16 transactions · 13 stateful · 2026-07-10 08:42:07 UTC

Parallelism

81/100

Blocked

54%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,804,705  ·  16 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

0x293c05d0…e8c5

0x34b655…2a6f

4 touches
1 conflict

0x45ea7a97…bbb3

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5b9e5ecc…2bc7

0x34b655…2a6f

4 touches
1 conflict

0x5f307189…61e6

0x34b655…2a6f

4 touches
1 conflict

0x72c8aeb2…9921

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0x293c05d013…6ee8c5

← previous block·next block →recent activity