← previous blocknext block →recent activity

Analyzing

Block #73,956,476

23 transactions · 15 stateful · 2026-05-11 20:05:35 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,956,476  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…0015

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xba5743c7…21c1

0x1b6862…e19c

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x7301f2af…c48e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

6 touches
3 conflicts

0x74fc6499…3543

0xd32edf…ff58

5 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: 0x1b68626d…2de19c

3 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity