← previous blocknext block →recent activity

Analyzing

Block #87,712,254

23 transactions · 21 stateful · 2026-07-14 13:51:07 UTC

Parallelism

78/100

Blocked

38%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,712,254  ·  23 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

0xbf78ee7f…e7fd

0x34b655…2a6f

8 touches
6 conflicts

0x5ec64628…72e4

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1aa71067…e40a

0x34b655…2a6f

4 touches
1 conflict

0x2fdfa032…139c

0x34b655…2a6f

4 touches
1 conflict

0x363a4317…87d2

0x34b655…2a6f

4 touches
1 conflict

0x3bb64385…bc41

0x34b655…2a6f

4 touches
1 conflict

0x3be29374…1df9

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 0xbf78ee7fb5…b5e7fd

← previous block·next block →recent activity