← previous blocknext block →recent activity

Analyzing

Block #86,793,789

19 transactions · 17 stateful · 2026-07-10 07:29:08 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,793,789  ·  19 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x1c03f81f…b304

0x34b655…2a6f

4 touches
1 conflict

0x2bcdd4a1…3d3a

0x34b655…2a6f

4 touches
1 conflict

0x3a6290da…e683

0x34b655…2a6f

4 touches
1 conflict

0x41bd2e6b…e240

0x34b655…2a6f

4 touches
1 conflict

0x453f53a8…e541

0x34b655…2a6f

4 touches
1 conflict

0x472c9167…63a5

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

6 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity