← previous blocknext block →recent activity

Analyzing

Block #87,417,613

30 transactions · 22 stateful · 2026-07-13 05:00:01 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,417,613  ·  30 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

0x2b5101ac…090b

0x34b655…2a6f

8 touches
6 conflicts

0x5ad8135f…d8e6

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x2145086e…39c6

0x34b655…2a6f

4 touches
1 conflict

0x26824212…7064

0x34b655…2a6f

4 touches
1 conflict

0x347327ff…3863

0x34b655…2a6f

4 touches
1 conflict

0x511cdf65…47ab

0x34b655…2a6f

4 touches
1 conflict

0x5238dcb7…e0e2

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 0x2b5101acd1…7c090b

← previous block·next block →recent activity