← previous blocknext block →recent activity

Analyzing

Block #86,233,193

21 transactions · 17 stateful · 2026-07-07 17:01:19 UTC

Parallelism

86/100

Blocked

41%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,233,193  ·  21 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

0x85eb1316…bb9e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x17c44db3…8888

0xa6afd3…d132

4 touches
1 conflict

0x2d94ecd9…43db

0x34b655…2a6f

4 touches
1 conflict

0xac0b4a08…faae

0x34b655…2a6f

4 touches
1 conflict

0xcda18b0b…6a4c

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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 0x85eb131679…60bb9e

← previous block·next block →recent activity