← previous blocknext block →recent activity

Analyzing

Block #86,981,941

23 transactions · 22 stateful · 2026-07-11 04:26:57 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,981,941  ·  23 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

0x17c3727d…cb0e

0x34b655…2a6f

6 touches
3 conflicts

0x775a8ad3…8307

0x34b655…2a6f

6 touches
3 conflicts

0x1941b441…5889

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xfcdb5918…2b49

0x34b655…2a6f

6 touches
3 conflicts

0x4e3abeff…18eb

0x34b655…2a6f

6 touches
3 conflicts

0xc3e19352…2faf

0x34b655…2a6f

6 touches
3 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

6 touches
3 conflicts

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 0x17c3727da3…18cb0e

← previous block·next block →recent activity