← previous blocknext block →recent activity

Analyzing

Block #87,672,037

16 transactions · 11 stateful · 2026-07-14 09:21:59 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #87,672,037  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5a36d0c8…12e3

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0xb3ae4660…5f75

0x34b655…2a6f

4 touches
1 conflict

0xc8f4deb0…dcf3

0x34b655…2a6f

4 touches
1 conflict

0x5a36d0c8…12e2

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0xf5e110b5…e26b

0x34b655…2a6f

3 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

1 conflict on slot 0x5a36d0c873…e212e3

← previous block·next block →recent activity