← previous blocknext block →recent activity

Analyzing

Block #74,425,737

18 transactions · 15 stateful · 2026-05-14 00:09:58 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

0.72

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,425,737  ·  18 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

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x9568555a…eb82

0x065c9d…c394

6 touches
3 conflicts

0xe483d4e3…e52e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xb17f1700…9322

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: 0x754704bc…afb603

6 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity