← previous blocknext block →recent activity

Analyzing

Block #86,681,117

25 transactions · 22 stateful · 2026-07-09 18:56:47 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,681,117  ·  25 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x015c6c43…fa58

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x855b877a…ae0c

0x34b655…2a6f

6 touches
3 conflicts

0x93c3b3b3…faf9

0x34b655…2a6f

6 touches
3 conflicts

0x015c6c43…fa59

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a9

0xb1dbf0…c0d3

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

10 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity