← previous blocknext block →recent activity

Analyzing

Block #86,708,931

19 transactions · 16 stateful · 2026-07-09 22:02:20 UTC

Parallelism

89/100

Blocked

25%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,708,931  ·  19 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

0xf6971361…0e3e

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xcee65b7c…a411

0x34b655…2a6f

4 touches
1 conflict

0xd8d890e3…99fe

0x34b655…2a6f

4 touches
1 conflict

0xde5e6db3…2e24

0x34b655…2a6f

4 touches
1 conflict

0xf45f2405…c8f9

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x0a6a5b44…d0e5

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 0xf697136182…e90e3e

← previous block·next block →recent activity