← previous blocknext block →recent activity

Analyzing

Block #74,416,599

28 transactions · 23 stateful · 2026-05-13 23:09:09 UTC

Parallelism

86/100

Blocked

48%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,416,599  ·  28 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

0x859d9943…e1fa

0xd32edf…ff58

7 touches
6 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

4 touches
1 conflict

0x24b79a65…9056

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641c

0x34b655…2a6f

4 touches
1 conflict

0x6af306bb…2e81

0x3bd359…433a

4 touches
1 conflict

0xce8bbe33…b72e

0x3bd359…433a

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 0x859d99436a…38e1fa

← previous block·next block →recent activity