← previous blocknext block →recent activity

Analyzing

Block #87,737,489

24 transactions · 22 stateful · 2026-07-14 16:40:04 UTC

Parallelism

79/100

Blocked

32%

Avg conflicts / tx

0.46

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,737,489  ·  24 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

0x46e3da6b…72ca

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x1ee46b22…9374

0x34b655…2a6f

4 touches
1 conflict

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x35cfae1b…c1f8

0x34b655…2a6f

4 touches
1 conflict

0x5ec64628…72e4

0x34b655…2a6f

4 touches
1 conflict

0x7c6cfc14…9957

0x34b655…2a6f

4 touches
1 conflict

0x7c6cfc14…9958

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 0x46e3da6bf9…ac72ca

← previous block·next block →recent activity