← previous blocknext block →recent activity

Analyzing

Block #87,710,501

37 transactions · 36 stateful · 2026-07-14 13:39:23 UTC

Parallelism

68/100

Blocked

58%

Avg conflicts / tx

1.81

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #87,710,501  ·  37 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0xa0a5bed4…1d15

0x34b655…2a6f

10 touches
10 conflicts

0xf5ea108a…dbf6

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xcfaa395f…5b1c

0x34b655…2a6f

8 touches
6 conflicts

0xe60e9000…c058

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity