← previous blocknext block →recent activity

Analyzing

Block #87,303,053

38 transactions · 33 stateful · 2026-07-12 16:13:48 UTC

Parallelism

76/100

Blocked

70%

Avg conflicts / tx

2.21

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,303,053  ·  38 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

0xfaef08b1…0696

0x34b655…2a6f

16 touches
28 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

14 touches
21 conflicts

0x216ffe66…1f94

0x34b655…2a6f

14 touches
21 conflicts

0x94e7f277…471b

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0x04fdea…47d7

10 touches
10 conflicts

0x3923cd2c…e6d3

0x34b655…2a6f

10 touches
10 conflicts

0x3c0e49c9…7833

0x34b655…2a6f

10 touches
10 conflicts

0xc7cda03f…b9da

0x34b655…2a6f

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

← previous block·next block →recent activity