← previous blocknext block →recent activity

Analyzing

Block #86,808,940

12 transactions · 11 stateful · 2026-07-10 09:10:24 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,808,940  ·  12 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

0xe5f54eb6…08bc

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x0ae9d2df…f787

0x34b655…2a6f

4 touches
1 conflict

0x0ae9d2df…f788

0x34b655…2a6f

4 touches
1 conflict

0x6c826b3b…5293

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x94ba9c4a…41d8

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 0xe5f54eb62d…0908bc

← previous block·next block →recent activity