← previous blocknext block →recent activity

Analyzing

Block #74,787,026

13 transactions · 11 stateful · 2026-05-15 16:25:52 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,787,026  ·  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

0x07bfd719…802d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

4 touches
1 conflict

0xa7477eac…c855

0x065c9d…c394

3 touches
1 conflict

0x48701497…8e9d

0x065c9d…c394

3 touches
1 conflict

0x2d6d7d9f…e273

0x065c9d…c394

3 touches
1 conflict

0x9725d73a…de08

0x065c9d…c394

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

1 conflict on slot 0x07bfd71937…1a802d

← previous block·next block →recent activity