← previous blocknext block →recent activity

Analyzing

Block #74,527,007

16 transactions · 13 stateful · 2026-05-14 11:26:03 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,527,007  ·  16 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2e2214a9…fe0d

0x5d823e…89c6

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x5d823e…89c6

4 touches
1 conflict

0x50997ada…364d

0x5d823e…89c6

4 touches
1 conflict

0x3819059d…362e

0x065c9d…c394

4 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity