← previous blocknext block →recent activity

Analyzing

Block #74,415,452

8 transactions · 7 stateful · 2026-05-13 23:01:29 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,415,452  ·  8 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0722ccc4…a09c

0x065c9d…c394

2 touches
0 conflicts

0x3d8654fd…b61b

0x065c9d…c394

2 touches
0 conflicts

0x7c8a33b6…4def

0x065c9d…c394

2 touches
0 conflicts

0x82c4a57e…322c

0x065c9d…c394

2 touches
0 conflicts

0xa3a770a5…4f4d

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