← previous blocknext block →recent activity

Analyzing

Block #74,502,579

16 transactions · 13 stateful · 2026-05-14 08:41:31 UTC

Parallelism

75/100

Blocked

31%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,502,579  ·  16 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0x08943ea2…ed03

0x754704…b603

4 touches
1 conflict

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0xb668ef98…7624

0xd32edf…ff58

3 touches
1 conflict

0x5d04d611…f1fc

0x065c9d…c394

2 touches
0 conflicts

0x2f77f0f6…4a92

0x188d58…ea8e

2 touches
0 conflicts

0x2f77f0f6…4a93

0x188d58…ea8e

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: 0x754704bc…afb603

3 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity