← previous blocknext block →recent activity

Analyzing

Block #87,710,428

18 transactions · 16 stateful · 2026-07-14 13:38:53 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,710,428  ·  18 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

0xcfaa395f…5b1c

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x5b37bb6b…ab00

0x34b655…2a6f

4 touches
1 conflict

0x5ec64628…72e4

0x34b655…2a6f

4 touches
1 conflict

0x8bf661cb…bcd2

0x34b655…2a6f

4 touches
1 conflict

0xa3a621f8…75a2

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 0xcfaa395f15…df5b1c

← previous block·next block →recent activity