← previous blocknext block →recent activity

Analyzing

Block #87,524,515

24 transactions · 20 stateful · 2026-07-13 16:55:29 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.75

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,524,515  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3439dfbc…0d03

0x34b655…2a6f

8 touches
6 conflicts

0x0eac6378…36f4

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe8352ac7…d7a3

0x34b655…2a6f

6 touches
3 conflicts

0x41d9a134…ccfe

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 0x3439dfbcc6…080d03

← previous block·next block →recent activity