← previous blocknext block →recent activity

Analyzing

Block #87,059,525

25 transactions · 24 stateful · 2026-07-11 13:05:22 UTC

Parallelism

60/100

Blocked

54%

Avg conflicts / tx

1.6

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,059,525  ·  25 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xa08f40b2…9a93

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x676d5418…85ea

0x34b655…2a6f

8 touches
6 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

8 touches
6 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

8 touches
6 conflicts

0x5bb46f6c…7693

0x34b655…2a6f

8 touches
6 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 0xa08f40b255…099a93

← previous block·next block →recent activity