← previous blocknext block →recent activity

Analyzing

Block #86,531,178

19 transactions · 18 stateful · 2026-07-09 02:11:50 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,531,178  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x38d19a60…c141

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x7a6681a8…c81c

0x34b655…2a6f

4 touches
1 conflict

0xb0bc3bf8…e2b1

0x34b655…2a6f

4 touches
1 conflict

0xbbb9fa77…d121

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity