← previous blocknext block →recent activity

Analyzing

Block #86,782,844

24 transactions · 21 stateful · 2026-07-10 06:16:05 UTC

Parallelism

71/100

Blocked

57%

Avg conflicts / tx

1.46

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,782,844  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0xdc921364…4680

0x34b655…2a6f

8 touches
6 conflicts

0xba4d47a9…0d84

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0004

0xb1dbf0…c0d3

8 touches
6 conflicts

0x63c900f4…2600

0x34b655…2a6f

6 touches
3 conflicts

0x727fbce7…0c80

0x34b655…2a6f

6 touches
3 conflicts

0x79d50d4a…951d

0x34b655…2a6f

6 touches
3 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

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

15 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity