← previous blocknext block →recent activity

Analyzing

Block #74,413,646

13 transactions · 10 stateful · 2026-05-13 22:49:32 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,413,646  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x581dbb66…5e20

0x065c9d…c394

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xf2f4176d…53e5

0xd32edf…ff58

3 touches
1 conflict

0x6477dd67…e2de

0x0594c7…a3be

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

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: 0x065c9d28…a9c394

1 conflict on slot 0x581dbb664b…685e20

← previous block·next block →recent activity