← previous blocknext block →recent activity

Analyzing

Block #87,760,521

22 transactions · 21 stateful · 2026-07-14 19:14:07 UTC

Parallelism

45/100

Blocked

57%

Avg conflicts / tx

3.14

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #87,760,521  ·  22 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x0733be30…112f

0x34b655…2a6f

20 touches
45 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

16 touches
28 conflicts

0xa0a5bed4…1d15

0x34b655…2a6f

16 touches
28 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xf3d10975…0d07

0x34b655…2a6f

12 touches
15 conflicts

0x92385428…6941

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

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

45 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity