← previous blocknext block →recent activity

Analyzing

Block #74,968,466

14 transactions · 10 stateful · 2026-05-16 12:37:43 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,968,466  ·  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

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0xbad8a49d…6398

0x065c9d…c394

4 touches
1 conflict

0x810a3aa2…0227

0x34b655…2a6f

4 touches
1 conflict

0x4c39e758…5a38

0x065c9d…c394

3 touches
1 conflict

0x392403ab…eba6

0x065c9d…c394

3 touches
1 conflict

0x551057cd…3c97

0x065c9d…c394

2 touches
0 conflicts

0x5d3e0b5b…dea0

0x065c9d…c394

2 touches
0 conflicts

0xa082c7df…a64b

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 0xba38536db1…342b7d

← previous block·next block →recent activity