← previous blocknext block →recent activity

Analyzing

Block #87,304,523

20 transactions · 18 stateful · 2026-07-12 16:23:38 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,304,523  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

12 touches
15 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x64aaadbf…f9f3

0x34b655…2a6f

8 touches
6 conflicts

0x37ee30c9…9e70

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x9a2de05d…3e6b

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2d

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

← previous block·next block →recent activity