← previous blocknext block →recent activity

Analyzing

Block #74,650,938

14 transactions · 13 stateful · 2026-05-15 01:16:48 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,650,938  ·  14 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

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0xffe431af…8faa

0x065c9d…c394

4 touches
1 conflict

0xfe7a24af…4dec

0x065c9d…c394

4 touches
1 conflict

0x13fb143f…8415

0x065c9d…c394

4 touches
1 conflict

0xa892b78a…e043

0x065c9d…c394

3 touches
1 conflict

0x1a506558…f645

0x065c9d…c394

3 touches
1 conflict

0x75f3f80e…fdef

0x065c9d…c394

3 touches
1 conflict

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

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity