← previous blocknext block →recent activity

Analyzing

Block #86,781,428

20 transactions · 20 stateful · 2026-07-10 06:06:40 UTC

Parallelism

65/100

Blocked

40%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,781,428  ·  20 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

0x7aad02c6…b979

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0xa6b89ebb…a66e

0x34b655…2a6f

8 touches
6 conflicts

0xf2f4727d…cdb7

0x34b655…2a6f

6 touches
3 conflicts

0x564e8dbe…da8b

0x34b655…2a6f

4 touches
1 conflict

0x5ff769f0…d2f6

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0x7aad02c682…feb979

← previous block·next block →recent activity