← previous blocknext block →recent activity

Analyzing

Block #87,695,082

23 transactions · 19 stateful · 2026-07-14 11:55:58 UTC

Parallelism

78/100

Blocked

37%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,695,082  ·  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

0x62222abd…e410

0x34b655…2a6f

10 touches
10 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x0e403c18…eac8

0x34b655…2a6f

4 touches
1 conflict

0x158becdc…73ed

0x34b655…2a6f

4 touches
1 conflict

0x17332fb4…cb06

0x34b655…2a6f

4 touches
1 conflict

0x53f393fa…00b9

0x34b655…2a6f

4 touches
1 conflict

0x55a476ed…ce14

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

10 conflicts on slot 0x62222abdea…6fe410

← previous block·next block →recent activity