← previous blocknext block →recent activity

Analyzing

Block #87,626,880

22 transactions · 20 stateful · 2026-07-14 04:20:14 UTC

Parallelism

73/100

Blocked

45%

Avg conflicts / tx

0.77

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,626,880  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x04c1786f…3ee6

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc514314c…1aa4

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x17c70f19…23a7

0x34b655…2a6f

4 touches
1 conflict

0x1ae78ca0…5cca

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 0x04c1786f74…073ee6

← previous block·next block →recent activity