← previous blocknext block →recent activity

Analyzing

Block #86,194,889

29 transactions · 21 stateful · 2026-07-07 12:45:28 UTC

Parallelism

90/100

Blocked

29%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,194,889  ·  29 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

0xafd867b7…2b2d

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2e

0x34b655…2a6f

4 touches
1 conflict

0xe8eae8a3…bacc

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0002

0x04fdea…47d7

4 touches
1 conflict

0x034f1f86…4e8d

0x34b655…2a6f

4 touches
1 conflict

0x3a5e841b…2190

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 0xafd867b7ed…d92b2d

← previous block·next block →recent activity