← previous blocknext block →recent activity

Analyzing

Block #74,765,481

19 transactions · 16 stateful · 2026-05-15 14:01:45 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,765,481  ·  19 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

0xeebee0c9…6aea

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0xab6260b4…69f0

0x065c9d…c394

2 touches
0 conflicts

0xb5d230a8…3fec

0x065c9d…c394

2 touches
0 conflicts

0xe7db977f…0659

0x065c9d…c394

2 touches
0 conflicts

0xfbb9e008…3165

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: 0xd32edf66…9fff58

6 conflicts on slot 0xeebee0c9e1…3b6aea

← previous block·next block →recent activity