← previous blocknext block →recent activity

Analyzing

Block #74,624,262

14 transactions · 12 stateful · 2026-05-14 22:19:04 UTC

Parallelism

79/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,624,262  ·  14 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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x2e71495e…b327

0x065c9d…c394

2 touches
0 conflicts

0x600c4848…d7ae

0x065c9d…c394

2 touches
0 conflicts

0x7c1a4d31…ee15

0x065c9d…c394

2 touches
0 conflicts

0x889ae798…6762

0x065c9d…c394

2 touches
0 conflicts

0xbbe3312c…7de0

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity