← previous blocknext block →recent activity

Analyzing

Block #74,331,524

12 transactions · 9 stateful · 2026-05-13 13:43:01 UTC

Parallelism

75/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,331,524  ·  12 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x7e5f2b3f…f3ed

0x065c9d…c394

4 touches
1 conflict

0x7ee87818…178c

0x065c9d…c394

3 touches
1 conflict

0x62d9cc4d…037a

0x065c9d…c394

3 touches
1 conflict

0xd585e071…d9e8

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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