← previous blocknext block →recent activity

Analyzing

Block #74,298,598

20 transactions · 15 stateful · 2026-05-13 10:04:03 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,298,598  ·  20 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

0xb4fe24f0…0f20

0xd32edf…ff58

7 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

4 touches
1 conflict

0x1bc9b1ca…85ef

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0xdf7899c0…c53a

0x34b655…2a6f

4 touches
1 conflict

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: 0xd32edf66…9fff58

6 conflicts on slot 0xb4fe24f0ab…050f20

← previous block·next block →recent activity