← previous blocknext block →recent activity

Analyzing

Block #74,920,382

9 transactions · 7 stateful · 2026-05-16 07:15:19 UTC

Parallelism

56/100

Blocked

43%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,920,382  ·  9 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0xbaedf3af…2186

0xd32edf…ff58

3 touches
1 conflict

0x087623af…728b

0x065c9d…c394

2 touches
0 conflicts

0x2b4ad252…8098

0x065c9d…c394

2 touches
0 conflicts

0x348fda08…7e96

0x065c9d…c394

2 touches
0 conflicts

0x543ad1ac…1661

0x065c9d…c394

2 touches
0 conflicts

0x61e7fa2a…302a

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