← previous blocknext block →recent activity

Analyzing

Block #87,671,861

32 transactions · 29 stateful · 2026-07-14 09:20:49 UTC

Parallelism

66/100

Blocked

48%

Avg conflicts / tx

2.06

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,671,861  ·  32 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x22e0cc1d…ad0d

0x34b655…2a6f

18 touches
36 conflicts

0x5170a218…3a84

0xc8689a…ee79

16 touches
28 conflicts

0x2fdfa032…139c

0x34b655…2a6f

16 touches
28 conflicts

0xdbb43016…7cc4

0x34b655…2a6f

16 touches
28 conflicts

0xa457c06e…2f06

0x34b655…2a6f

16 touches
28 conflicts

0x68c6b2fa…098d

0x34b655…2a6f

16 touches
28 conflicts

0x8412088a…7005

0x34b655…2a6f

16 touches
28 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

16 touches
28 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

36 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity