← previous blocknext block →recent activity

Analyzing

Block #74,034,080

16 transactions · 13 stateful · 2026-05-12 04:44:23 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,034,080  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x0b390c61…dc07

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x73fc93b7…7afb

0x065c9d…c394

6 touches
3 conflicts

0xb2ffdf59…cb25

0x065c9d…c394

5 touches
3 conflicts

0x42535762…413d

0x065c9d…c394

3 touches
1 conflict

0xe75ce681…ba60

0x188d58…ea8e

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity