← previous blocknext block →recent activity

Analyzing

Block #86,773,360

22 transactions · 19 stateful · 2026-07-10 05:12:52 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,773,360  ·  22 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

0x945befa9…67b4

0x34b655…2a6f

6 touches
3 conflicts

0xce827910…ff22

0x065c9d…c394

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x1c796c6b…064e

0x34b655…2a6f

4 touches
1 conflict

0x2fae5b2e…2367

0x34b655…2a6f

4 touches
1 conflict

0x5036f376…c06a

0x34b655…2a6f

4 touches
1 conflict

0x62b13313…bbe8

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 0x945befa9d4…8867b4

← previous block·next block →recent activity