← previous blocknext block →recent activity

Analyzing

Block #86,250,275

21 transactions · 19 stateful · 2026-07-07 18:55:30 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,250,275  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb56f0740…7542

0x34b655…2a6f

4 touches
1 conflict

0xbdd72ed7…e23a

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf195ad96…e0c3

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x9228e31f…02ff

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 0xb56f0740e2…c17542

← previous block·next block →recent activity