← previous blocknext block →recent activity

Analyzing

Block #87,785,538

24 transactions · 24 stateful · 2026-07-14 22:01:32 UTC

Parallelism

58/100

Blocked

54%

Avg conflicts / tx

2.13

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,785,538  ·  24 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

0x00000000…000b

0x90c374…be45

20 touches
45 conflicts

0x00000000…000a

0x90c374…be45

20 touches
45 conflicts

0x10a2bd5d…ad6d

0x8d1565…6723

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0xd0ec60a1…d246

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x4a870d86…79ef

0x336ed4…c59c

6 touches
3 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: 0x90c3747c…0ebe45

45 conflicts on slot 0x0000000000…00000b

← previous block·next block →recent activity