← previous blocknext block →recent activity

Analyzing

Block #74,204,534

16 transactions · 13 stateful · 2026-05-12 23:38:31 UTC

Parallelism

69/100

Blocked

54%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,204,534  ·  16 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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x1a366f9d…beb4

0xd32edf…ff58

7 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001e

0x1b6862…e19c

2 touches
0 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: 0x2a68ba18…8e90c5

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity