← previous blocknext block →recent activity

Analyzing

Block #87,703,397

21 transactions · 18 stateful · 2026-07-14 12:51:47 UTC

Parallelism

71/100

Blocked

39%

Avg conflicts / tx

0.57

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,703,397  ·  21 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

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x93b6fab0…09d6

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4a4

0x34b655…2a6f

6 touches
3 conflicts

0xb3e53c5e…b99c

0x34b655…2a6f

6 touches
3 conflicts

0xba4af1d1…be28

0x34b655…2a6f

6 touches
3 conflicts

0xd708bac6…2e5d

0x34b655…2a6f

6 touches
3 conflicts

0xe60e9000…c058

0x34b655…2a6f

6 touches
3 conflicts

0x0090639e…243e

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 0x92385428ad…dc6941

← previous block·next block →recent activity