← previous blocknext block →recent activity

Analyzing

Block #87,292,053

26 transactions · 25 stateful · 2026-07-12 15:00:18 UTC

Parallelism

62/100

Blocked

56%

Avg conflicts / tx

2.15

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,292,053  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xfaef08b1…0696

0x34b655…2a6f

18 touches
36 conflicts

0x922c7ebd…6600

0xc8689a…ee79

16 touches
28 conflicts

0x727fbce7…0c80

0x34b655…2a6f

16 touches
28 conflicts

0x7506443a…4820

0x34b655…2a6f

16 touches
28 conflicts

0x7523ad90…2ba5

0x34b655…2a6f

16 touches
28 conflicts

0xc0b9bd73…7f1c

0x34b655…2a6f

16 touches
28 conflicts

0xc368d7fd…aaec

0x34b655…2a6f

16 touches
28 conflicts

0xcfa965cc…6fcf

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 0xfaef08b108…f90696

← previous block·next block →recent activity