← previous blocknext block →recent activity

Analyzing

Block #86,952,132

20 transactions · 19 stateful · 2026-07-11 01:07:45 UTC

Parallelism

65/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,952,132  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xb06917e8…6985

0x34b655…2a6f

6 touches
3 conflicts

0xd93edb3f…94ec

0x34b655…2a6f

6 touches
3 conflicts

0xa6b89ebb…a66e

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x8712f56f…a277

0x34b655…2a6f

6 touches
3 conflicts

0x8a1db511…3ac9

0x34b655…2a6f

6 touches
3 conflicts

0x68c07cb9…ae14

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity