← previous blocknext block →recent activity

Analyzing

Block #74,333,560

25 transactions · 16 stateful · 2026-05-13 13:56:33 UTC

Parallelism

88/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,333,560  ·  25 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x73912233…4583

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x728f999a…832f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xcfe3a9a4…0d35

0xd32edf…ff58

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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: 0x34b6552d…112a6f

3 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity