← previous blocknext block →recent activity

Analyzing

Block #87,731,664

26 transactions · 21 stateful · 2026-07-14 16:01:07 UTC

Parallelism

65/100

Blocked

43%

Avg conflicts / tx

0.92

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,731,664  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x255ba9f3…396d

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0xa55c4598…2988

0x34b655…2a6f

6 touches
3 conflicts

0x79277877…6098

0x34b655…2a6f

4 touches
1 conflict

0x96a0de78…a2a6

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