← previous blocknext block →recent activity

Analyzing

Block #74,338,710

16 transactions · 12 stateful · 2026-05-13 14:30:51 UTC

Parallelism

81/100

Blocked

25%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,338,710  ·  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

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xbe164143…68d7

0xd32edf…ff58

3 touches
1 conflict

0x52363343…1cf5

0x065c9d…c394

2 touches
0 conflicts

0x57366cb4…80ab

0x065c9d…c394

2 touches
0 conflicts

0x86b4f3b9…2008

0x065c9d…c394

2 touches
0 conflicts

0x8e7c8609…dbd7

0x065c9d…c394

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 0x0000000000…00003d

← previous block·next block →recent activity