← previous blocknext block →recent activity

Analyzing

Block #86,930,792

16 transactions · 11 stateful · 2026-07-10 22:45:11 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,930,792  ·  16 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

0xfffe583a…9130

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x1af19f5c…aee2

0x34b655…2a6f

4 touches
1 conflict

0x55125205…f0ff

0x34b655…2a6f

4 touches
1 conflict

0x552ac70a…d74b

0x34b655…2a6f

4 touches
1 conflict

0x5691b1ff…f64c

0x34b655…2a6f

4 touches
1 conflict

0x56b5f5c0…a3ad

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 0xfffe583a09…d59130

← previous block·next block →recent activity