← previous blocknext block →recent activity

Analyzing

Block #74,506,088

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

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,506,088  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbab4a9f9…107f

0x065c9d…c394

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0x52363343…1cf5

0x065c9d…c394

3 touches
1 conflict

0x754d7319…8a9e

0x065c9d…c394

2 touches
0 conflicts

0xa22d4a11…7c5e

0x065c9d…c394

2 touches
0 conflicts

0xa7915a4a…f2b4

0x065c9d…c394

2 touches
0 conflicts

0xfd475b8a…9439

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 0xbab4a9f9b8…99107f

← previous block·next block →recent activity