← previous blocknext block →recent activity

Analyzing

Block #74,465,242

18 transactions · 14 stateful · 2026-05-14 04:32:59 UTC

Parallelism

78/100

Blocked

21%

Avg conflicts / tx

0.22

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,465,242  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0xfbeac08b…ec6d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0xd49762c9…1359

0x34b655…2a6f

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

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: 0x34b6552d…112a6f

3 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity