← previous blocknext block →recent activity

Analyzing

Block #86,836,479

20 transactions · 17 stateful · 2026-07-10 12:14:42 UTC

Parallelism

55/100

Blocked

59%

Avg conflicts / tx

1.2

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,836,479  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x9f40a209…1193

0x34b655…2a6f

8 touches
6 conflicts

0xc0b9bd73…7f1c

0x34b655…2a6f

8 touches
6 conflicts

0xc8c54a2d…0f66

0x34b655…2a6f

8 touches
6 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