← previous blocknext block →recent activity

Analyzing

Block #87,518,567

17 transactions · 16 stateful · 2026-07-13 16:15:16 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,518,567  ·  17 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

0xc335872c…4214

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x157dbfb2…4089

0x34b655…2a6f

4 touches
1 conflict

0x1cabef0c…30d4

0x34b655…2a6f

4 touches
1 conflict

0x1ec7ada6…505b

0x34b655…2a6f

4 touches
1 conflict

0x326f2a00…a2a6

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0xc335872cc4…8e4214

← previous block·next block →recent activity