← previous blocknext block →recent activity

Analyzing

Block #87,693,145

13 transactions · 12 stateful · 2026-07-14 11:43:03 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,693,145  ·  13 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x09dddc76…e12a

0x34b655…2a6f

4 touches
1 conflict

0x3dcbc94a…a380

0x34b655…2a6f

4 touches
1 conflict

0x48e6f054…d2ac

0x34b655…2a6f

4 touches
1 conflict

0x49f75237…44f4

0x34b655…2a6f

4 touches
1 conflict

0x4f51d069…d0b4

0x34b655…2a6f

4 touches
1 conflict

0x51087f5a…61f7

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 0xc824469a90…af6425

← previous block·next block →recent activity