← previous blocknext block →recent activity

Analyzing

Block #87,408,714

20 transactions · 20 stateful · 2026-07-13 04:00:27 UTC

Parallelism

75/100

Blocked

40%

Avg conflicts / tx

1.15

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,408,714  ·  20 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

0x4cabb80a…46bf

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x734ee320…caae

0x34b655…2a6f

8 touches
6 conflicts

0x69ce640b…884a

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x34731dbd…e467

0x34b655…2a6f

6 touches
3 conflicts

0x5e51fa73…5cc9

0x34b655…2a6f

6 touches
3 conflicts

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 0x4cabb80a0e…7546bf

← previous block·next block →recent activity