← previous blocknext block →recent activity

Analyzing

Block #74,506,948

13 transactions · 11 stateful · 2026-05-14 09:10:56 UTC

Parallelism

85/100

Blocked

36%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,506,948  ·  13 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

0xd30aecc0…3c75

0x065c9d…c394

4 touches
1 conflict

0x140b9466…1bc2

0x065c9d…c394

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xa058effb…4d24

0x065c9d…c394

3 touches
1 conflict

0x106ef211…e21e

0x065c9d…c394

3 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

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

1 conflict on slot 0xd30aecc0ed…f73c75

← previous block·next block →recent activity