← previous blocknext block →recent activity

Analyzing

Block #87,708,852

26 transactions · 24 stateful · 2026-07-14 13:28:21 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.73

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,708,852  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x5170a218…3a84

0xc8689a…ee79

6 touches
3 conflicts

0x015c28a0…37da

0x34b655…2a6f

6 touches
3 conflicts

0x727fbce7…0c80

0x34b655…2a6f

6 touches
3 conflicts

0xa1111a1a…f235

0x34b655…2a6f

6 touches
3 conflicts

0xaa3b52b3…20bf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0xc1ff9f…b0fc

6 touches
3 conflicts

0xd98b3c10…67b8

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity