← previous blocknext block →recent activity

Analyzing

Block #87,356,094

19 transactions · 19 stateful · 2026-07-12 22:08:29 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,356,094  ·  19 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

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x87f7a54b…4e66

0xd32edf…ff58

5 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0xa1bfcc4c…f2db

0x851145…3f07

4 touches
1 conflict

0xc2e36a04…b85e

0x851145…3f07

4 touches
1 conflict

0xc948dbdc…199a

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 0x737acb7813…fafce8

← previous block·next block →recent activity