← previous blocknext block →recent activity

Analyzing

Block #87,758,922

23 transactions · 21 stateful · 2026-07-14 19:03:25 UTC

Parallelism

61/100

Blocked

52%

Avg conflicts / tx

1.74

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,758,922  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x49f5a697…72c0

0x34b655…2a6f

16 touches
28 conflicts

0xf3d10975…0d07

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x7fb99184…e8bb

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x7c6cfc14…9958

0x34b655…2a6f

8 touches
6 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

28 conflicts on slot 0x49f5a69781…bc72c0

← previous block·next block →recent activity