← previous blocknext block →recent activity

Analyzing

Block #87,638,561

16 transactions · 14 stateful · 2026-07-14 05:38:22 UTC

Parallelism

75/100

Blocked

64%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,638,561  ·  16 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

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0b1cc6d1…1f59

0x851145…3f07

5 touches
3 conflicts

0x56a919c4…ab49

0x01bff4…1071

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x703b861a…cbe3

0x188d58…ea8e

4 touches
1 conflict

0x703b861a…cbe4

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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 0x0733be30d6…38112f

← previous block·next block →recent activity