← previous blocknext block →recent activity

Analyzing

Block #74,430,620

16 transactions · 15 stateful · 2026-05-14 00:42:28 UTC

Parallelism

69/100

Blocked

40%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,430,620  ·  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

0xcf0021d2…4432

0xd32edf…ff58

7 touches
6 conflicts

0x91220b8f…7a04

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0xf82d6b5a…2afa

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

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: 0xd32edf66…9fff58

6 conflicts on slot 0xcf0021d200…224432

← previous block·next block →recent activity