← previous blocknext block →recent activity

Analyzing

Block #74,468,359

9 transactions · 8 stateful · 2026-05-14 04:53:42 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,468,359  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x847d5b61…c544

0x065c9d…c394

4 touches
1 conflict

0x446b79da…9cf6

0x065c9d…c394

3 touches
1 conflict

0xaca345bb…350e

0x065c9d…c394

3 touches
1 conflict

0x8b0c6712…f2dc

0x065c9d…c394

2 touches
0 conflicts

0xa1b6c64b…2849

0x065c9d…c394

2 touches
0 conflicts

0xf0cceadb…c8b0

0x065c9d…c394

2 touches
0 conflicts

0xff9593c7…ed75

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

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: 0x065c9d28…a9c394

1 conflict on slot 0x847d5b6127…31c544

← previous block·next block →recent activity