← previous blocknext block →recent activity

Analyzing

Block #86,233,854

20 transactions · 17 stateful · 2026-07-07 17:05:44 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,233,854  ·  20 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

0x422d5490…52d9

0x34b655…2a6f

6 touches
3 conflicts

0xb12b4474…702d

0x065c9d…c394

4 touches
1 conflict

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x1c796c6b…064e

0x34b655…2a6f

4 touches
1 conflict

0x205a3a98…a8d7

0x34b655…2a6f

4 touches
1 conflict

0x36a2423d…e290

0x34b655…2a6f

4 touches
1 conflict

0x388f889f…a655

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 0x422d549061…1f52d9

← previous block·next block →recent activity