← previous blocknext block →recent activity

Analyzing

Block #74,650,891

9 transactions · 8 stateful · 2026-05-15 01:16:29 UTC

Parallelism

78/100

Blocked

25%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,650,891  ·  9 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

0xfe7a24af…4dec

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x13fb143f…8415

0x065c9d…c394

3 touches
1 conflict

0x08a8f3a2…8a47

0x065c9d…c394

3 touches
1 conflict

0x4c9f4e07…b5b3

0x065c9d…c394

2 touches
0 conflicts

0x5cb735e4…8ff5

0x065c9d…c394

2 touches
0 conflicts

0x64abf2ac…43b8

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

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 0xfe7a24af03…774dec

← previous block·next block →recent activity