← previous blocknext block →recent activity

Analyzing

Block #74,455,841

18 transactions · 11 stateful · 2026-05-14 03:30:25 UTC

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,455,841  ·  18 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

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x3fb12dd2…cb8b

0x065c9d…c394

4 touches
1 conflict

0x613a7157…07e8

0x065c9d…c394

3 touches
1 conflict

0x26af1b06…f8b7

0x065c9d…c394

2 touches
0 conflicts

0x38b373f7…3109

0x065c9d…c394

2 touches
0 conflicts

0x62147975…cc1e

0x065c9d…c394

2 touches
0 conflicts

0x71ffdb10…1fb5

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

← previous block·next block →recent activity