← previous blocknext block →recent activity

Analyzing

Block #86,217,214

21 transactions · 17 stateful · 2026-07-07 15:14:38 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,217,214  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x75bcb28b…31e1

0x34b655…2a6f

4 touches
1 conflict

0x7618d94e…2ec3

0x34b655…2a6f

4 touches
1 conflict

0xa233e6a5…5939

0x34b655…2a6f

4 touches
1 conflict

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe8eae8a3…bacc

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: 0x681e908b…e1ae09

1 conflict on slot 0x0d622e34f9…000000

← previous block·next block →recent activity