← previous blocknext block →recent activity

Analyzing

Block #74,390,615

17 transactions · 11 stateful · 2026-05-13 20:16:10 UTC

Parallelism

88/100

Blocked

9%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,390,615  ·  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

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…006f

0x1efe02…37d6

2 touches
0 conflicts

0x6c08213a…e5a8

0x1efe02…37d6

2 touches
0 conflicts

0x83a484e1…1f43

0x1efe02…37d6

2 touches
0 conflicts

0xf1c07b7e…c5f7

0x1efe02…37d6

2 touches
0 conflicts

0xf853eb8e…401e

0x34b655…2a6f

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: 0xea1b8e4a…8fc5ec

1 conflict on slot 0xb6b74ae0ff…d48d5e

← previous block·next block →recent activity