← previous blocknext block →recent activity

Analyzing

Block #87,588,605

19 transactions · 18 stateful · 2026-07-14 00:04:16 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,588,605  ·  19 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

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xd2453506…54e4

0x34b655…2a6f

6 touches
3 conflicts

0x0b826166…904e

0x34b655…2a6f

4 touches
1 conflict

0x17cc5ec3…ae0e

0x34b655…2a6f

4 touches
1 conflict

0x1f2cd70b…94be

0x34b655…2a6f

4 touches
1 conflict

0x27bfe98b…2053

0x34b655…2a6f

4 touches
1 conflict

0x2b5101ac…090b

0x34b655…2a6f

4 touches
1 conflict

0x2fc56154…d632

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

6 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity