← previous blocknext block →recent activity

Analyzing

Block #74,040,869

13 transactions · 12 stateful · 2026-05-12 05:29:36 UTC

Parallelism

77/100

Blocked

42%

Avg conflicts / tx

0.62

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,040,869  ·  13 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0001

0x5c533c…a5a6

4 touches
1 conflict

0x92c60916…fe4d

0x065c9d…c394

2 touches
0 conflicts

0x9c8c9939…2fb3

0x065c9d…c394

2 touches
0 conflicts

0xadbc5b90…22c4

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity