← previous blocknext block →recent activity

Analyzing

Block #87,709,341

30 transactions · 23 stateful · 2026-07-14 13:31:37 UTC

Parallelism

77/100

Blocked

43%

Avg conflicts / tx

0.9

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,709,341  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x0a0cecef…4ed0

0x34b655…2a6f

4 touches
1 conflict

0x12a84469…2bea

0x34b655…2a6f

4 touches
1 conflict

0x4560e5a8…b741

0x34b655…2a6f

4 touches
1 conflict

0x55cf4758…265c

0x34b655…2a6f

4 touches
1 conflict

0x67905f6e…02a1

0x34b655…2a6f

4 touches
1 conflict

0x6c2aa5be…d808

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