← previous blocknext block →recent activity

Analyzing

Block #87,708,210

26 transactions · 23 stateful · 2026-07-14 13:24:03 UTC

Parallelism

69/100

Blocked

39%

Avg conflicts / tx

0.92

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,708,210  ·  26 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

0x64aaadbf…f9f3

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x680ca7d7…2df4

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x37ee30c9…9e70

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x2cd98078…527c

0x34b655…2a6f

4 touches
1 conflict

0x87bdb64a…593a

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

15 conflicts on slot 0x64aaadbf0a…79f9f3

← previous block·next block →recent activity