← previous blocknext block →recent activity

Analyzing

Block #74,361,035

10 transactions · 10 stateful · 2026-05-13 16:59:16 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,361,035  ·  10 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

0x47b807a2…3307

0x065c9d…c394

6 touches
3 conflicts

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x8aed1474…4973

0xd32edf…ff58

3 touches
1 conflict

0x656f208d…141a

0x065c9d…c394

3 touches
1 conflict

0x0297f37e…ab8a

0x065c9d…c394

3 touches
1 conflict

0x4341432b…ad29

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

3 conflicts on slot 0x47b807a243…c53307

← previous block·next block →recent activity