← previous blocknext block →recent activity

Analyzing

Block #87,757,008

21 transactions · 21 stateful · 2026-07-14 18:50:37 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,757,008  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x41f1e2e5…2edf

0x34b655…2a6f

6 touches
3 conflicts

0x80630fb9…a436

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x367b69ad…33d9

0x34b655…2a6f

4 touches
1 conflict

0x5a7eb2ab…75a0

0x34b655…2a6f

4 touches
1 conflict

0x67d8b378…f2f8

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity