← previous blocknext block →recent activity

Analyzing

Block #87,520,235

24 transactions · 20 stateful · 2026-07-13 16:26:32 UTC

Parallelism

67/100

Blocked

45%

Avg conflicts / tx

0.92

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,520,235  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x17cc5ec3…ae0e

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xca18c58e…cede

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0xb5f244d5…f550

0x34b655…2a6f

6 touches
3 conflicts

0xad0c7701…1d83

0x34b655…2a6f

4 touches
1 conflict

0xb1c67a7d…b9b1

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

6 conflicts on slot 0x17cc5ec39e…57ae0e

← previous block·next block →recent activity