← previous blocknext block →recent activity

Analyzing

Block #74,352,455

28 transactions · 21 stateful · 2026-05-13 16:02:09 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,352,455  ·  28 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

0xb0a7000f…5e0f

0xd32edf…ff58

9 touches
10 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0xb6993963…e147

0x065c9d…c394

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x62e20208…be65

0x0555e3…2b9c

4 touches
1 conflict

0x00000000…0000

0x094452…0a09

4 touches
1 conflict

0x00000000…0002

0x094452…0a09

4 touches
1 conflict

0x00000000…0004

0x094452…0a09

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

10 conflicts on slot 0xb0a7000f18…7a5e0f

← previous block·next block →recent activity