← previous blocknext block →recent activity

Analyzing

Block #86,489,132

24 transactions · 22 stateful · 2026-07-08 21:31:16 UTC

Parallelism

67/100

Blocked

41%

Avg conflicts / tx

0.75

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,489,132  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x59dccbd8…2bf6

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc948dbdc…199a

0x34b655…2a6f

6 touches
3 conflicts

0x08c952c6…69b1

0x34b655…2a6f

4 touches
1 conflict

0x0ab54c30…b88e

0x34b655…2a6f

4 touches
1 conflict

0x11560115…bfc2

0x34b655…2a6f

4 touches
1 conflict

0x24d58d14…f7a5

0x34b655…2a6f

4 touches
1 conflict

0x282fd1fa…1fca

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 0x59dccbd857…c52bf6

← previous block·next block →recent activity