← previous blocknext block →recent activity

Analyzing

Block #74,734,996

10 transactions · 8 stateful · 2026-05-15 10:37:54 UTC

Parallelism

80/100

Blocked

25%

Avg conflicts / tx

0.4

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,734,996  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xfa0de845…c401

0x065c9d…c394

4 touches
1 conflict

0xa3fa79fd…0175

0x065c9d…c394

4 touches
1 conflict

0x1ae85053…1b7b

0x065c9d…c394

3 touches
1 conflict

0x91f41802…a65a

0x065c9d…c394

3 touches
1 conflict

0x1ae85053…1b7a

0x065c9d…c394

3 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

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

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity