← previous blocknext block →recent activity

Analyzing

Block #87,713,497

20 transactions · 19 stateful · 2026-07-14 13:59:25 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,713,497  ·  20 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

0x0733be30…112f

0x34b655…2a6f

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x560ed681…07e6

0x34b655…2a6f

8 touches
6 conflicts

0x3a996b35…bc8f

0x34b655…2a6f

8 touches
6 conflicts

0x149ea1fb…e34a

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x64800813…db9f

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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

15 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity