← previous blocknext block →recent activity

Analyzing

Block #74,648,855

22 transactions · 15 stateful · 2026-05-15 01:02:55 UTC

Parallelism

68/100

Blocked

53%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,648,855  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xffe431af…8faa

0x065c9d…c394

8 touches
6 conflicts

0x09875205…62cf

0xd32edf…ff58

7 touches
6 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0x24887e8c…c8e7

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

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

6 conflicts on slot 0xffe431af56…838faa

← previous block·next block →recent activity