← previous blocknext block →recent activity

Analyzing

Block #87,671,137

27 transactions · 22 stateful · 2026-07-14 09:15:58 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,671,137  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x11d629eb…bcd9

0x34b655…2a6f

6 touches
3 conflicts

0xb0446875…2b96

0x34b655…2a6f

6 touches
3 conflicts

0x1274880c…3cdc

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x249d8bcb…69b9

0x34b655…2a6f

4 touches
1 conflict

0x487aa334…7ef2

0x34b655…2a6f

4 touches
1 conflict

0x68c6b2fa…098d

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

10 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity