← previous blocknext block →recent activity

Analyzing

Block #86,250,088

18 transactions · 14 stateful · 2026-07-07 18:54:14 UTC

Parallelism

89/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,250,088  ·  18 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

0x217a0f43…5d80

0x34b655…2a6f

4 touches
1 conflict

0x5c338ec4…da65

0x34b655…2a6f

4 touches
1 conflict

0x6eac5a5d…1730

0x34b655…2a6f

4 touches
1 conflict

0x7a2fc410…c088

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2578f3dc…b3d7

0x2a68ba…90c5

4 touches
1 conflict

0x0c366266…77e1

0x34b655…2a6f

4 touches
1 conflict

0x10d9dbcb…9fdb

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 0x217a0f438d…e75d80

← previous block·next block →recent activity