← previous blocknext block →recent activity

Analyzing

Block #87,503,814

23 transactions · 18 stateful · 2026-07-13 14:36:24 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,503,814  ·  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

0x39a45f01…2b79

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0001

0xc1ff9f…b0fc

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x26bcd08c…8b42

0x34b655…2a6f

4 touches
1 conflict

0x32ae718c…1437

0x34b655…2a6f

4 touches
1 conflict

0x3439dfbc…0d03

0x34b655…2a6f

4 touches
1 conflict

0x3a6290da…e683

0x34b655…2a6f

4 touches
1 conflict

0x3c8d99a5…b937

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 0x39a45f0156…d32b79

← previous block·next block →recent activity