← previous blocknext block →recent activity

Analyzing

Block #74,455,861

18 transactions · 10 stateful · 2026-05-14 03:30:33 UTC

Parallelism

89/100

Blocked

10%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x5db1ecb7…490f

0x065c9d…c394

2 touches
0 conflicts

0x68f8818a…de0b

0x065c9d…c394

2 touches
0 conflicts

0x6dca549a…502f

0x065c9d…c394

2 touches
0 conflicts

0xda99ffda…527f

0x065c9d…c394

2 touches
0 conflicts

0xf0d602fe…e634

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

← previous block·next block →recent activity