← previous blocknext block →recent activity

Analyzing

Block #86,627,940

22 transactions · 20 stateful · 2026-07-09 13:00:19 UTC

Parallelism

68/100

Blocked

45%

Avg conflicts / tx

1.09

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,627,940  ·  22 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

12 touches
15 conflicts

0x22bc4ea4…5c8a

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x60c7217a…8c94

0x34b655…2a6f

6 touches
3 conflicts

0x6b2ba712…0214

0x34b655…2a6f

6 touches
3 conflicts

0x7523ad90…2ba5

0x34b655…2a6f

6 touches
3 conflicts

0x976795c2…d0ce

0x34b655…2a6f

6 touches
3 conflicts

0x9ad66bbf…929c

0x34b655…2a6f

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity