← previous blocknext block →recent activity

Analyzing

Block #74,040,979

14 transactions · 11 stateful · 2026-05-12 05:30:19 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,040,979  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8ab66b07…e301

0x065c9d…c394

4 touches
1 conflict

0x775ae6c1…5eba

0x065c9d…c394

4 touches
1 conflict

0xac1a0564…e0b7

0x065c9d…c394

3 touches
1 conflict

0xc04bf9a8…e1f2

0x065c9d…c394

3 touches
1 conflict

0xe0363e53…017e

0x065c9d…c394

3 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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity