← previous blocknext block →recent activity

Analyzing

Block #74,340,852

14 transactions · 12 stateful · 2026-05-13 14:45:05 UTC

Parallelism

86/100

Blocked

8%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,340,852  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…009a

0x16f70c…c3dd

2 touches
0 conflicts

0x72a152dd…9e1b

0x16f70c…c3dd

2 touches
0 conflicts

0xea02471d…1539

0x34b655…2a6f

2 touches
0 conflicts

0x2d153e58…4eac

0x58e158…3d57

2 touches
0 conflicts

0xd130ecdb…1c3b

0x58e158…3d57

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 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity