← previous blocknext block →recent activity

Analyzing

Block #74,456,897

26 transactions · 17 stateful · 2026-05-14 03:37:28 UTC

Parallelism

81/100

Blocked

53%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,456,897  ·  26 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

0xd623cadb…d6da

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0x6fd9ae7c…e981

0x1b6862…e19c

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5cfec795…7c0e

0x34b655…2a6f

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 0xd623cadb0f…fed6da

← previous block·next block →recent activity