← previous blocknext block →recent activity

Analyzing

Block #74,671,503

14 transactions · 13 stateful · 2026-05-15 03:34:17 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,671,503  ·  14 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

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xa35e9ea4…a3df

0xd32edf…ff58

3 touches
1 conflict

0x3054cee9…bbd4

0x065c9d…c394

2 touches
0 conflicts

0x42d9f26b…a98d

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x490b34bd…61d7

0x065c9d…c394

2 touches
0 conflicts

0xef363e4a…00e4

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: 0xab35264b…1cfa38

1 conflict on slot 0x0000000000…000002

← previous block·next block →recent activity