← previous blocknext block →recent activity

Analyzing

Block #74,388,967

13 transactions · 12 stateful · 2026-05-13 20:05:12 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,388,967  ·  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

0x8cc18498…ce7e

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x628927fe…7f2c

0x1efe02…37d6

2 touches
0 conflicts

0x3dbd9177…e936

0xea1b8e…c5ec

2 touches
0 conflicts

0x455b104f…3960

0xea1b8e…c5ec

2 touches
0 conflicts

0x9c8d6dd6…d619

0xea1b8e…c5ec

2 touches
0 conflicts

0x9c8d6dd6…d61a

0xea1b8e…c5ec

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

1 conflict on slot 0x8cc18498cc…52ce7e

← previous block·next block →recent activity