← previous blocknext block →recent activity

Analyzing

Block #74,458,649

13 transactions · 9 stateful · 2026-05-14 03:49:07 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,458,649  ·  13 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0f9a3a01…08e7

0x065c9d…c394

2 touches
0 conflicts

0x244224e3…cdb3

0x065c9d…c394

2 touches
0 conflicts

0x94dd717a…0f8f

0x065c9d…c394

2 touches
0 conflicts

0x95e8153a…f21e

0x065c9d…c394

2 touches
0 conflicts

0xacd3df5f…2079

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity