← previous blocknext block →recent activity

Analyzing

Block #74,336,200

17 transactions · 11 stateful · 2026-05-13 14:14:07 UTC

Parallelism

88/100

Blocked

9%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,336,200  ·  17 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

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x2061c258…694c

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x341138d9…dc19

0x065c9d…c394

2 touches
0 conflicts

0x499d41bd…0ef3

0x065c9d…c394

2 touches
0 conflicts

0x4e642fb7…c127

0x065c9d…c394

2 touches
0 conflicts

0x50276521…1f03

0x065c9d…c394

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x765c236f2d…b5ff45

← previous block·next block →recent activity