← previous blocknext block →recent activity

Analyzing

Block #74,447,544

10 transactions · 8 stateful · 2026-05-14 02:35:07 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,447,544  ·  10 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

0xcd3b36c5…584c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x283a9549…68d7

0x065c9d…c394

2 touches
0 conflicts

0x32881b99…5494

0x065c9d…c394

2 touches
0 conflicts

0x6b59c822…eaa4

0x065c9d…c394

2 touches
0 conflicts

0xb318c164…4283

0x065c9d…c394

2 touches
0 conflicts

0xb35ae359…bc7f

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: 0x065c9d28…a9c394

1 conflict on slot 0xcd3b36c507…40584c

← previous block·next block →recent activity