← previous blocknext block →recent activity

Analyzing

Block #87,357,621

25 transactions · 23 stateful · 2026-07-12 22:18:40 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,357,621  ·  25 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

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0x0733be30…112f

0x34b655…2a6f

10 touches
10 conflicts

0xf4ff6152…dac9

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xb678410a…0edb

0x34b655…2a6f

4 touches
1 conflict

0xd6113c0f…0a4b

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity