← previous blocknext block →recent activity

Analyzing

Block #87,704,837

20 transactions · 18 stateful · 2026-07-14 13:01:28 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,704,837  ·  20 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

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x236375e3…00bd

0x34b655…2a6f

4 touches
1 conflict

0x548145a9…cfce

0x34b655…2a6f

4 touches
1 conflict

0x5ec64628…72e4

0x34b655…2a6f

4 touches
1 conflict

0x709cb1f7…ed38

0x34b655…2a6f

4 touches
1 conflict

0x7c0bdc54…9dde

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

21 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity