← previous blocknext block →recent activity

Analyzing

Block #74,504,914

16 transactions · 14 stateful · 2026-05-14 08:57:12 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,504,914  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x92cecaf8…402f

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x7728060a…f401

0x065c9d…c394

3 touches
1 conflict

0x367ce492…deb1

0x065c9d…c394

3 touches
1 conflict

0x6ed01d45…cdaf

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001c

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

1 conflict on slot 0x92cecaf8ec…13402f

← previous block·next block →recent activity